This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

debugging dynamically loadable code


Hello, hope this is not off-topic,
I need to debug some code that is located in a dynamic library, a .so file. 
This file is loaded by a program at run-time (with dlopen I supouse). So I 
load this program into gdb (using ddd) and my problem is that I can't open 
the yet-unloaded sources and/or set a break point on them.
If I run the program to let it load the .so file it'll be too late because I 
need to debug the module initialization code.
I know I should put a breakpoint between the loading and the running of the 
module, but I can't find it. The module is loaded thru a custom script this 
application interprets, so, it's hard to dig that code.
Any ideas how can I do my debugging ?
Thank you.
-- 
Pupeno <pupeno@pupeno.com> (http://pupeno.com)

Attachment: pgp00000.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]