From: Bert D. <dri...@pl...> - 2004-06-23 12:42:09
|
On Tue, 22 Jun 2004, Eric Smith wrote: > Scott wrote: > > Probably a > > convenient place would be to set one at cmd_help(). > > Do you mean cmd_help::cmd_help()? If I try to set a breakpoint there, > it says there are two functions (due to overloading). I tell it to > set breaks on all. But it thinks the addresses of those functions are > zero, so it doesn't work. Below is the session log. What I do is to add a dummy routine after the call to dlopen (in src/modules.cc): void my_dummy_breakpoint() { } handle = dlopen (library_name, RTLD_LAZY); my_dummy_breakpoint(); (if I'm lazy, I use atan(0) for the dummy call). Then, the gdb invocation becomes: gdb gpsim gdb> b main gdb> run Break at main ... gdb> b atan gdb> c Break at atan gdb> break at whatever_i_want_to_debug gdb> c But, as usual, there is more than one way to skin a cat. Cheers, -- Bert -- Bert Driehuis -- dri...@pl... -- +31-20-3116119 If the only tool you've got is an axe, every problem looks like fun! |