From owner-freebsd-current  Tue Sep 18 12: 9:14 2001
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1])
	by hub.freebsd.org (Postfix) with ESMTP id 09BEC37B401
	for <current@FreeBSD.ORG>; Tue, 18 Sep 2001 12:09:12 -0700 (PDT)
Received: from [207.76.207.129] (PBG4.whistle.com [207.76.207.129])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA98021;
	Tue, 18 Sep 2001 12:08:55 -0700 (PDT)
Mime-Version: 1.0
X-Sender: mark-ml@207.76.206.1
Message-Id: <p05100301b7cd4bb73799@[207.76.207.129]>
In-Reply-To: <20010918092248.A666@laptop.6bone.nl>
References: <20010916101828.B455@dhcp01.pn.xcllnt.net>
 <3BA4EE76.2AED07FA@elischer.org> <20010918092248.A666@laptop.6bone.nl>
Date: Tue, 18 Sep 2001 12:08:57 -0700
To: Mark Santcroos <marks@ripe.net>, peter@wemm.org
From: Mark Peek <mark@whistle.com>
Subject: Re: gdb(1) broken?
Cc: current@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

At 9:22 AM +0200 9/18/01, Mark Santcroos wrote:
>Hi Peter,
>
>What is the state of this (for i386)?
>
>Mark
>
>On Sun, Sep 16, 2001 at 11:24:54AM -0700, Julian Elischer wrote:
>>  Marcel Moolenaar wrote:
>>  >
>>  > 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?
>>
>>  peter has been working on this...
>>
>  > It's because the process structure and u-area have changed entirely.


I just checked in a change to fix this problem 
(sys/kern/sys_process.c v1.71). The KSE changes caused the trace 
information to be put into the debug process state instead of the 
traced process.

Mark

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message