[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

r2908 - in glibc-package/trunk/debian: . debhelper.in



Author: aurel32
Date: 2008-04-06 09:28:01 +0000 (Sun, 06 Apr 2008)
New Revision: 2908

Added:
   glibc-package/trunk/debian/debhelper.in/libc-prof.README.Debian
Modified:
   glibc-package/trunk/debian/changelog
Log:
  * debhelper.in/libc-prof.README.Debian: new file to explain how to use
    libc-prof.  Closes: #442858.



Modified: glibc-package/trunk/debian/changelog
===================================================================
--- glibc-package/trunk/debian/changelog	2008-04-05 22:06:53 UTC (rev 2907)
+++ glibc-package/trunk/debian/changelog	2008-04-06 09:28:01 UTC (rev 2908)
@@ -13,12 +13,14 @@
     locks witch gcc-4.3.
   * patches/any/cvs-rfc3484.diff: update tests from CVS.  Closes: #474226.
   * patches/localedata/locale-shs_CA.diff: add Secwepemctsín from CVS.
+  * debhelper.in/libc-prof.README.Debian: new file to explain how to use
+    libc-prof.  Closes: #442858.
 
   [ Pierre Habouzit ]
   * Add any/cvs-strerror_r.diff to make strerror_r actually thread safe.
     Closes: #456531.
 
- -- Aurelien Jarno <aurel32@debian.org>  Sat, 05 Apr 2008 22:38:25 +0200
+ -- Aurelien Jarno <aurel32@debian.org>  Sun, 06 Apr 2008 11:26:50 +0200
 
 glibc (2.7-10) unstable; urgency=low
 

Added: glibc-package/trunk/debian/debhelper.in/libc-prof.README.Debian
===================================================================
--- glibc-package/trunk/debian/debhelper.in/libc-prof.README.Debian	                        (rev 0)
+++ glibc-package/trunk/debian/debhelper.in/libc-prof.README.Debian	2008-04-06 09:28:01 UTC (rev 2908)
@@ -0,0 +1,23 @@
+README.Debian for libc-prof
+---------------------------
+
+gprof is the GNU Profiler, a tool used when tracking which functions are
+eating CPU in your program. Anyway, you should already be familiar with
+it if you got interested by this package.
+
+This package provides a version of the GNU Libc compiled for profiling
+in order to get profiling information from standard library functions
+such as malloc, read or open.
+
+In order to use it, you have to use `-static-libgcc -lc_p' in addition 
+to the normal `-pg'. `-static-libgcc' is needed to ensure that libgcc
+does not pull the dynamic version of the GNU Libc.
+
+For instance here is how to compile and link myprog.c with profiling:
+  gcc -g -pg -o myprog.o -c myprog.c
+  gcc -pg -o myprog myprog.o -static-libgcc -lc_p
+
+This also works with a command that both compiles and links: 
+  gcc -g -pg -o myprog myprog.c -static-libgcc -lc_p
+
+ -- Aurelien Jarno <aurel32@debian.org>  Sun, 06 Apr 2008 11:28:25 +0200


Reply to: