aboutsummaryrefslogtreecommitdiff
path: root/gprof
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2009-01-03 10:00:58 +0000
committerNick Clifton <nickc@redhat.com>2009-01-03 10:00:58 +0000
commitc8d1c0af8062b171426f9dc64e895a39eb255146 (patch)
tree8b541adfe444e76efd15884ba399d59e04c29cb2 /gprof
parent4d78a120893392ff5feac12480e2bf94e3cc0dbb (diff)
downloadgdb-c8d1c0af8062b171426f9dc64e895a39eb255146.zip
gdb-c8d1c0af8062b171426f9dc64e895a39eb255146.tar.gz
gdb-c8d1c0af8062b171426f9dc64e895a39eb255146.tar.bz2
PR 7099
* gprof.texi (Compiling): Mention the need for using -static-libgcc on shared library systems.
Diffstat (limited to 'gprof')
-rw-r--r--gprof/ChangeLog6
-rw-r--r--gprof/gprof.texi14
2 files changed, 20 insertions, 0 deletions
diff --git a/gprof/ChangeLog b/gprof/ChangeLog
index 1d1f596..50b2ab2 100644
--- a/gprof/ChangeLog
+++ b/gprof/ChangeLog
@@ -1,3 +1,9 @@
+2009-01-03 Nick Clifton <nickc@redhat.com>
+
+ PR 7099
+ * gprof.texi (Compiling): Mention the need for using
+ -static-libgcc on shared library systems.
+
2009-01-02 Nick Clifton <nickc@redhat.com>
* po/id.po: Updated Indonesian translation.
diff --git a/gprof/gprof.texi b/gprof/gprof.texi
index f389087..1f86383 100644
--- a/gprof/gprof.texi
+++ b/gprof/gprof.texi
@@ -325,6 +325,20 @@ example:
ld -o myprog /lib/gcrt0.o myprog.o utils.o -lc_p
@end example
+If you are running the program on a system which supports shared
+libraries you may run into problems with the profiling support code in
+a shared library being called before that library has been fully
+initialised. This is usually detected by the program encountering a
+segmentation fault as soon as it is run. The solution is to link
+against a static version of the library containing the profiling
+support code, which for @code{gcc} users can be done via the
+@samp{-static} or @samp{-static-libgcc} command line option. For
+example:
+
+@example
+gcc -g -pg -static-libgcc myprog.c utils.c -o myprog
+@end example
+
If you compile only some of the modules of the program with @samp{-pg}, you
can still profile the program, but you won't get complete information about
the modules that were compiled without @samp{-pg}. The only information