This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: Help: Unwinding the C++ stack...throw, longjmp & threads
- To: drepper@cygnus.com
- Subject: Re: Help: Unwinding the C++ stack...throw, longjmp & threads
- From: Joern Rennecke <amylaar@cygnus.co.uk>
- Date: Wed, 25 Aug 1999 06:38:23 +0100 (BST)
- Cc: george@moberg.com, kriol@fnal.gov, gcc@gcc.gnu.org, libc-alpha@sourceware.CYGNUS.com
> + 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.