Blame SOURCES/memstomp-man.patch

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