Help: Unwinding the C++ stack...throw, longjmp & threads

Joern Rennecke amylaar@cygnus.co.uk
Tue Aug 24 22:39:00 GMT 1999


>   + functions which use callbacks and those directly or indirectly using
>     functions which use callbacks

This can be automated.  Hack gcc so that it logs function and file name
when code is compiled that dereferences a function pointer,
and compile glibc with this hacked gcc.
This gives you the functions that use callbacks.
Than you search for functions that use these functions, and in turn for
functions that use those functions, till no new functions are found.


More information about the Libc-alpha mailing list