Since it sounds like you are able to build
the failing module from source, you might
be able to have it cooperate with you in
your attempts to attach to it with GDB.
For example, you could add some code at the
beginning that would create a file with a
recognizable name in /tmp. Your code would
write your PID into that file and then stand
around waiting until that file no longer
exists before resuming "normal" operations.
Then when you run the failing app, you'd
wait until that file were created in /tmp,
start up an instance of GDB, tell it to
attach to that PID and then delete the file,
signalling the app to proceeed. When the
fault occurred GDB would halt the app and
allow you to look around.
If you're lucky you'll discover that you've
made the faulting reference in your own
code and can fix it immediately. On the
other hand you might discover that you've
tripped over a bug in some library code,
which would suck.
>GPL all the way: Sell services, don't lease secrets
Cool! Where do I send the bill?
Regards,
----------------------------------------
Michael O'Donnell [EMAIL PROTECTED]
----------------------------------------
###########################################
# This transmission has not been approved #
# by the Office of Homeland Security. #
###########################################
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
