Date: Wed, 20 Aug 1997 08:24:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: gdb: Program received signal SIGTRAP? Message-ID: <19970820082459.FC27103@uriah.heep.sax.de> In-Reply-To: <19970820122215.34114@lemis.com>; from Greg Lehey on Aug 20, 1997 12:22:15 %2B0930 References: <19970820122215.34114@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As 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. SIGTRAP means that gdb got a signal for a breakpoint it didn't set. This can happen if a fork() inherits a breakpoint (but i think this wouldn't show up in gdb, but only as a fatal signal to the child). Seems your context was something of a signal handler, so it wouldn't surprise me there, too. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970820082459.FC27103>