From owner-freebsd-hackers Tue Feb 17 01:25:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13994 for freebsd-hackers-outgoing; Tue, 17 Feb 1998 01:25:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13985 for ; Tue, 17 Feb 1998 01:25:07 -0800 (PST) (envelope-from toshok@netscape.com) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id BAA28578 for ; Tue, 17 Feb 1998 01:24:35 -0800 (PST) Received: from netscape.com ([205.217.243.66]) by dredd.mcom.com (Netscape Messaging Server 3.5) with ESMTP id AAA713E; Tue, 17 Feb 1998 01:24:33 -0800 Message-ID: <34E9574A.F0726589@netscape.com> Date: Tue, 17 Feb 1998 01:24:26 -0800 From: Chris Toshok X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: Greg Lehey CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Another problem with debugging the navigator on FreeBSD2.2-STABLE References: <34E3CE26.880FC190@netscape.com> <19980214112105.05348@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > 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 > > 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 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? > Heh :) Thanks for the offer, but I actually found the problem shortly after I sent the original mail. Turns out the the netscape thread library uses SIGALRM for some accounting stuff. All that was required was 'handle SIGALRM nopass'. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message