Blame SOURCES/memstomp-man.patch
aac10ca4b7efb5ef4f387ec64996d9bc0ff1278c
aac10c --- a/Makefile.am 2013-03-11 21:53:40.934186094 -0600aac10c +++ b/Makefile.am 2013-03-11 21:57:44.795212526 -0600aac10c @@ -34,6 +34,8 @@ lib_LTLIBRARIES = \aac10c bin_SCRIPTS = \aac10c memstompaac10c aac10c +man1_MANS = memstomp.manaac10c +aac10c CLEANFILES = \aac10c memstompaac10c aac10c diff -Nrup a/memstomp.man b/memstomp.manaac10c --- a/memstomp.man 1969-12-31 17:00:00.000000000 -0700aac10c +++ b/memstomp.man 2013-05-10 17:53:37.767722170 -0600aac10c @@ -0,0 +1,69 @@aac10c +.\" This is a commentaac10c +.\" Contact Owen@thelinuxblog.comaac10c +.TH MEMSTOMP 1 "09 April 2013" "0.1.4"aac10c +.SH NAMEaac10c +memstomp \- detect function calls with overlapping memory regionsaac10c +.SH SYNOPSISaac10c +.B memstompaac10c +.RB [ \-dk ]aac10c +.I applicationaac10c +.RI [ argument ...]aac10c +.PPaac10c +.B memstompaac10c +.B \-haac10c +.SH DESCRIPTIONaac10c +Theaac10c +.B memstompaac10c +utility identifies function calls that use overlapping memory regions in situations when such an overlap is not allowed by various standards. When a problem is detected, memstomp displays a backtrace to help you debug the problem, and if executed with theaac10c +.B \-\-debug\-infoaac10c +command line option, it even uses the available debugging information. Since the backtrace code is not thread safe, memstomp also allows you to use theaac10c +.B \-\-killaac10c +option to immediately terminate the analyzed program when an invalid function call is detected.aac10c +.PPaac10c +This version of memstomp inspects the following function calls:aac10c +.BR memcpy (),aac10c +.BR memccpy (),aac10c +.BR mempcpy (),aac10c +.BR strcpy (),aac10c +.BR stpcpy (),aac10c +.BR strncpy (),aac10c +.BR stpncpy (),aac10c +.BR strcat (),aac10c +.BR strncat (),aac10c +.BR wmemcpy (),aac10c +.BR wmempcpy (),aac10c +.BR wcscpy (),aac10c +.BR wcsncpy (),aac10c +.BR wcscat (),aac10c +andaac10c +.BR wcsncat ().aac10c +.SH OPTIONSaac10c +.TPaac10c +.BR \-d ", " \-\-debug\-infoaac10c +Make use of debugging information to produce more detailed stack traces.aac10c +.TPaac10c +.BR \-k ", " \-\-killaac10c +Kill the analyzed application when a problem is detected.aac10c +.TPaac10c +.BR \-h ", " \-\-helpaac10c +Display usage information and exit.aac10c +.SH SEE ALSOaac10c +.BR memcpy (3),aac10c +.BR memccpy (3),aac10c +.BR mempcpy (3),aac10c +.BR strcpy (3),aac10c +.BR stpcpy (3),aac10c +.BR strncpy (3),aac10c +.BR stpncpy (3),aac10c +.BR strcat (3),aac10c +.BR strncat (3),aac10c +.BR wmemcpy (3),aac10c +.BR wmempcpy (3),aac10c +.BR wcscpy (3),aac10c +.BR wcsncpy (3),aac10c +.BR wcscat (3),aac10c +.BR wcsncat (3)aac10c +.SH AUTHORSaac10c +Lennart Poettering <lennart@poettering.net>aac10c +.braac10c +William Cohen <wcohen@redhat.com>
