From owner-freebsd-current@FreeBSD.ORG Thu Aug 11 19:33:51 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1276116A41F for ; Thu, 11 Aug 2005 19:33:51 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id B328D43D55 for ; Thu, 11 Aug 2005 19:33:50 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.4/8.13.4) with ESMTP id j7BJXlm4004744; Thu, 11 Aug 2005 12:33:50 -0700 (PDT) (envelope-from marcel@xcllnt.net) In-Reply-To: <200508111052.01305.lonnie.vanzandt@ngc.com> References: <200508040940.56172.lonnie.vanzandt@ngc.com> <200508111009.53939.lonnie.vanzandt@ngc.com> <1E8A49C9-D0E7-43CF-A3AC-CEA50B1A3135@xcllnt.net> <200508111052.01305.lonnie.vanzandt@ngc.com> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 11 Aug 2005 12:33:46 -0700 To: lonnie.vanzandt@ngc.com X-Mailer: Apple Mail (2.733) Cc: current@freebsd.org Subject: Re: Missing a step in new(er) Remote gdb/kdb setup? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 19:33:51 -0000 On Aug 11, 2005, at 9:52 AM, Lonnie VanZandt wrote: > forgive me for grasping for straws, but, might I hope that those > fixes are > related to segfaults on initial connections? ;-) If so, what is > the nature > of the fix? Yes. The problem is that when support for -r was added, it was forgotten that the code so far assumed there was a KVM session open. With -r, kgdb does not open a KVM session. This causes various NULL-pointer dereferences. The fix is to check first if a KVM session is open and do whatever is appropriate in that case. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net