break points in dynamically loaded code on OSF/1 hangs system?!?

From: anthony baxter <anthony.baxter_at_aaii.oz.au>
Date: Wed, 06 Sep 1995 17:03:46 +1000

Hiya,

I'm attempting to debug some code on an OSF/1 3.2A system. The code in
question is dynamically loaded into a running interpreter (in this case,
the python interpreter). Ok, so I try this under gdb, decladebug, and
dbx.

both gdb and decladebug fail to let me put breakpoints inside the dynamically
loaded module - gdb just wont allow it, while decladebug will allow it, but
fails to stop at the breakpoint.

dbx will allow it. Unfortunately, doing this works fine, then I can happily
debug away, until I quit dbx, then the whole system freezes up. This _is_ a
bummer. It makes debugging slower if I have to reboot the machine each time
I quit dbx, and it's annoying the hell out of the person that the machine
belongs to.

On a 2.0 system, it works fine.

Has anyone seen anything like this at all? I could not find anything on
ftp.service.digital.com that sounded at all like the problem...

Thanks,
Anthony
Received on Wed Sep 06 1995 - 09:24:06 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT