Date: Thu, 11 Aug 2005 12:33:46 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: lonnie.vanzandt@ngc.com Cc: current@freebsd.org Subject: Re: Missing a step in new(er) Remote gdb/kdb setup? Message-ID: <B1FF6781-1F0E-42A5-8D9D-FCA0ACFC5AD5@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1FF6781-1F0E-42A5-8D9D-FCA0ACFC5AD5>