This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi! 2002-08-04 Jakub Jelinek <jakub@redhat.com> * manual/debug.texi: Fix spelling to programmatically. Reported by <hayastan132@hotmail.com>. --- libc/manual/debug.texi.jj 2001-05-23 09:21:44.000000000 +0200 +++ libc/manual/debug.texi 2002-08-04 21:57:15.000000000 +0200 @@ -26,7 +26,7 @@ locate the problem. A @dfn{backtrace} is a list of the function calls that are currently active in a thread. The usual way to inspect a backtrace of a program is to use an external debugger such as gdb. However, sometimes it is -useful to obtain a backtrace programatically from within a program, +useful to obtain a backtrace programmatically from within a program, e.g., for the purposes of logging or diagnostics. The header file @file{execinfo.h} declares three functions that obtain Jakub
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |