Oliver Elphick <olly@lfix.co.uk> writes:
> I have not been able to trace the program because I haven't yet worked
> out how to set breakpoints in a module loaded after the run command in
> gdb.
Set a breakpoint somewhere after the module will be loaded. Once the
module has been loaded, you can tell gdb about it with
gdb> sharedlibrary path-to-.so-file
Then you'll be able to set a breakpoint in the shared library.
(An annoyance here is that you can't restart the program from scratch
without losing this work and having to redo it. Grumble.)
At least, that works for me on HP-UX. I assume it's the same on all
gdb platforms ...
regards, tom lane
