From owner-freebsd-current Sun Sep 16 10:18:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 11D7B37B401 for ; Sun, 16 Sep 2001 10:18:06 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f8GHI5m81649 for ; Sun, 16 Sep 2001 10:18:05 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id f8GHIS100627 for current@FreeBSD.org; Sun, 16 Sep 2001 10:18:28 -0700 (PDT) (envelope-from marcel) Date: Sun, 16 Sep 2001 10:18:28 -0700 From: Marcel Moolenaar To: current@FreeBSD.org Subject: gdb(1) broken? Message-ID: <20010916101828.B455@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gang, I don't know exactly what the gdb(1) problems on Alpha are, but we do have a problem that's probably not specific to an architecture. The problem is basicly this: one cannot debug any programs because gdb(1) gets a SIGTRAP delivered when it invokes ptrace(2) and never gets a change to wait4(2) the "interior" process. I don't know the details, but one of the following can be the case 1. We now deliver a SIGTRAP, when we didn't do so before, 2. The SIGTRAP comes too quick, it should be "caught" by the wait4(2). I couldn't find any indication that 1 happened, so my guess is that we suffer from 2. Is this known? Any thoughts? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message