Stefan, Thanks for stepping in...
> I've looked at the proposed manual page and I have a > few comments (note that I haven't managed to use the > backtrace() functions correctly yet, so I'm not a > specialist): > > - the description for backtrace() sounds a bit off; > I'm not a native speaker of English, but "stores to > buffer" should probably be "stores ... in buffer". I am a native speaker, and I agree ;-). > Also, I don't think "most recently called functions" > is accurate - you could use "the list of active > function calls in the current thread", or "the > function call backtrace". Yes, better. > - there is a typo in the first paragraph of "RETURN > VALUE" - s/greater greater/greater. > - the glibc manual states a few more situations where > the stack trace will not be valid besides frame > pointer omission - function inlining can also make for > non exact stack traces. Yes. > - the last paragraph in the NOTES section should > probably be "The names of the functions are not > actually available unless you pass '-rdynamic' as an > option to gcc/g++ when compiling". Yes. > You might be right about -rdynamic, here's what the > gcc manual has to say about this option: > > "Pass the flag -export-dynamic to the ELF linker, on > targets that support it. This instructs the linker to > add all symbols, not only used ones, to the dynamic > symbol table. This option is needed for some uses of > dlopen or to allow obtaining backtraces from within a > program. " > > I will try to play with the functions myself, just to > see if -rdynamic yields the expected results. See my other mail. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/, read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
