Blame SOURCES/memstomp-man.patch
Branch: 6c066355a54694826d07a47ec3a0472205fc1d86
6c0663
--- a/Makefile.am 2013-03-11 21:53:40.934186094 -0600
6c0663
+++ b/Makefile.am 2013-03-11 21:57:44.795212526 -0600
6c0663
@@ -34,6 +34,8 @@ lib_LTLIBRARIES = \
6c0663
bin_SCRIPTS = \
6c0663
memstomp
6c0663
6c0663
+man1_MANS = memstomp.man
6c0663
+
6c0663
CLEANFILES = \
6c0663
memstomp
6c0663
6c0663
diff -Nrup a/memstomp.man b/memstomp.man
6c0663
--- a/memstomp.man 1969-12-31 17:00:00.000000000 -0700
6c0663
+++ b/memstomp.man 2013-05-10 17:53:37.767722170 -0600
6c0663
@@ -0,0 +1,69 @@
6c0663
+.\" This is a comment
6c0663
+.\" Contact Owen@thelinuxblog.com
6c0663
+.TH MEMSTOMP 1 "09 April 2013" "0.1.4"
6c0663
+.SH NAME
6c0663
+memstomp \- detect function calls with overlapping memory regions
6c0663
+.SH SYNOPSIS
6c0663
+.B memstomp
6c0663
+.RB [ \-dk ]
6c0663
+.I application
6c0663
+.RI [ argument ...]
6c0663
+.PP
6c0663
+.B memstomp
6c0663
+.B \-h
6c0663
+.SH DESCRIPTION
6c0663
+The
6c0663
+.B memstomp
6c0663
+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 the
6c0663
+.B \-\-debug\-info
6c0663
+command line option, it even uses the available debugging information. Since the backtrace code is not thread safe, memstomp also allows you to use the
6c0663
+.B \-\-kill
6c0663
+option to immediately terminate the analyzed program when an invalid function call is detected.
6c0663
+.PP
6c0663
+This version of memstomp inspects the following function calls:
6c0663
+.BR memcpy (),
6c0663
+.BR memccpy (),
6c0663
+.BR mempcpy (),
6c0663
+.BR strcpy (),
6c0663
+.BR stpcpy (),
6c0663
+.BR strncpy (),
6c0663
+.BR stpncpy (),
6c0663
+.BR strcat (),
6c0663
+.BR strncat (),
6c0663
+.BR wmemcpy (),
6c0663
+.BR wmempcpy (),
6c0663
+.BR wcscpy (),
6c0663
+.BR wcsncpy (),
6c0663
+.BR wcscat (),
6c0663
+and
6c0663
+.BR wcsncat ().
6c0663
+.SH OPTIONS
6c0663
+.TP
6c0663
+.BR \-d ", " \-\-debug\-info
6c0663
+Make use of debugging information to produce more detailed stack traces.
6c0663
+.TP
6c0663
+.BR \-k ", " \-\-kill
6c0663
+Kill the analyzed application when a problem is detected.
6c0663
+.TP
6c0663
+.BR \-h ", " \-\-help
6c0663
+Display usage information and exit.
6c0663
+.SH SEE ALSO
6c0663
+.BR memcpy (3),
6c0663
+.BR memccpy (3),
6c0663
+.BR mempcpy (3),
6c0663
+.BR strcpy (3),
6c0663
+.BR stpcpy (3),
6c0663
+.BR strncpy (3),
6c0663
+.BR stpncpy (3),
6c0663
+.BR strcat (3),
6c0663
+.BR strncat (3),
6c0663
+.BR wmemcpy (3),
6c0663
+.BR wmempcpy (3),
6c0663
+.BR wcscpy (3),
6c0663
+.BR wcsncpy (3),
6c0663
+.BR wcscat (3),
6c0663
+.BR wcsncat (3)
6c0663
+.SH AUTHORS
6c0663
+Lennart Poettering <lennart@poettering.net>
6c0663
+.br
6c0663
+William Cohen <wcohen@redhat.com>