Date: Wed, 20 Aug 1997 18:17:30 +0930 From: Greg Lehey <grog@lemis.com> To: Hans Zuidam <hans@brandinnovators.com> Cc: hackers@FreeBSD.ORG Subject: Re: gdb: Program received signal SIGTRAP? Message-ID: <19970820181730.19951@lemis.com> In-Reply-To: <199708200732.JAA21257@truk.brandinnovators.com>; from Hans Zuidam on Wed, Aug 20, 1997 at 09:32:27AM %2B0200 References: <19970820122215.34114@lemis.com> <199708200732.JAA21257@truk.brandinnovators.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 20, 1997 at 09:32:27AM +0200, Hans Zuidam wrote: >> Greg Lehey wrote: >> Has anybody seen problems with gdb where you can't continue from a >> breakpoint? I'm currently trying to test user ppp, but once I hit a >> breakpoint, I can't continue. I'm running -current as of yesterday. >> Here's a sample: >> Program received signal SIGTRAP, Trace/breakpoint trap. >> DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 >> 773 if (been_here_before) /* we won't be able to do it again, */ >> (gdb) >> Cannot insert breakpoint 0: >> Error accessing memory address 0xefbfdfdc: Bad address. > This is probably because your process (ppp) is corrupting its stack. > gdb examines to processes stack to find proper stack frames when > inserting/removing breakpoint. If the stack is corrupted gdb gets > very confused. Really? I can't recall seeing that. In any case, the process is not corrupting its stack. If I don't set the breakpoint, it runs fine. It could be that I've shot myself in the foot, though: I updated to -current of this morning, but didn't do a make world, though I did make gdb, so that's not the immediate problem. I'm doing a make world now, and will try again afterwards. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970820181730.19951>