On Thu, 12 February 1998 at 20:37:58 -0800, Chris Toshok wrote:
> 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
> Program received signal SIGTRAP, Trace/breakpoint trap.
> foo_nsFunction (foo=0x0) at foofile.c:192
> 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 should do. Are you sure that this is the real problem?
> 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?
Good question. Can you give me a binary to look at?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message