Date: Thu, 12 Feb 1998 20:37:58 -0800 From: Chris Toshok <toshok@netscape.com> To: freebsd-hackers@FreeBSD.ORG Subject: Another problem with debugging the navigator on FreeBSD2.2-STABLE Message-ID: <34E3CE26.880FC190@netscape.com>
next in thread | raw e-mail | index | archive | help
So, I've gotten around my complete inability to even *run* gdb on the navigator, but now I've got another problem: When I hit a breakpoint and try to either step or continue, I see: (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. foo_nsFunction (foo=0x0) at foofile.c:192 (gdb) The problem is, the breakpoint is at the same place at which the program just stopped. The only way to get past this breakpoint is to disable the breakpoint and continue. Disabling the breakpoing and stepping doesn't work. It's getting pretty frustrating, trying to debug a large amount of code by setting breakpoints at just about every line of a function and disabling one and then enabling another. Anyone got an idea what could be causing this? Debugging other programs works fine. I would imagine that the size of the program and it's shared libraries is part of the problem, but what can I do to fix it? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34E3CE26.880FC190>