https://bugs.kde.org/show_bug.cgi?id=193597
--- Comment #2 from Gareth McCaughan <gareth mccaughan pobox com> 2009-05-23 03:41:08 --- Unfortunately, attempting to attach gdb (version 6.1.1, in case it matters) to either the kio_smtp process or the klauncher process doesn't do anything useful for me. I've tried two ways. Firstly, just with -p [process ID]. That gives me this internal error: /usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/solib-svr4.c:1443: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled. A problem internal to GDB has been detected, further debugging may prove unreliable. which I get again if I ask it not to quit. After that, gdb just sits there doing nothing. (I'm guessing that it's trying to talk to the process I've asked it to debug, which isn't responding because it's too busy waiting for a lock it's never going to get.) If instead I provide gdb with a path to the kdeinit4 executable (that's the right thing for attaching to kio_smtp, yesno?) I don't get the errors; instead gdb goes straight to sitting there ignoring me. (In both cases, gdb is not killable with ctrl-C, but I can e.g. ctrl-Z it and then kill the gdb process.) My gdb-fu is pretty weak and I may very well be missing something simple. Is there some cleverer way I could get a backtrace? Any point poking at the process's /proc entry in search of its stack, or anything? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
