From owner-freebsd-current@FreeBSD.ORG Thu Aug 11 16:14:40 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 9331F16A433 for ; Thu, 11 Aug 2005 16:14:40 +0000 (GMT) (envelope-from Lonnie.Vanzandt@ngc.com) Received: from xcgca810.northgrum.com (xcgca810.northgrum.com [208.12.122.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8200E43D5A for ; Thu, 11 Aug 2005 16:14:38 +0000 (GMT) (envelope-from Lonnie.Vanzandt@ngc.com) Received: from xcgca800.northgrum.com ([157.127.103.70]) by xcgca810.northgrum.com with InterScan Messaging Security Suite; Thu, 11 Aug 2005 09:14:33 -0700 Received: from xcgco501.northgrum.com ([158.114.104.53]) by xcgca800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 11 Aug 2005 09:14:33 -0700 Received: from [192.168.217.128] ([158.114.106.12]) by xcgco501.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 11 Aug 2005 10:14:28 -0600 From: Lonnie VanZandt Organization: Northrop Grumman To: Marcel Moolenaar , current@freebsd.org Date: Thu, 11 Aug 2005 10:09:53 -0600 User-Agent: KMail/1.8.1 References: <200508040940.56172.lonnie.vanzandt@ngc.com> <200508041027.38635.lonnie.vanzandt@ngc.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508111009.53939.lonnie.vanzandt@ngc.com> X-OriginalArrivalTime: 11 Aug 2005 16:14:28.0211 (UTC) FILETIME=[BF9BFC30:01C59E8F] Cc: 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 Reply-To: lonnie.vanzandt@ngc.com 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 16:14:40 -0000 Marcel, The protocol sync issue is now gone - but the host side kgdb core dumps immediately after reporting the current break point of the target: lonnie@aperiodic$ kgdb -r /dev/cuaa0 /tmp/kernel.debug [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". (no debugging symbols found)...Switching to remote protocol 0xc0634d14 in kdb_enter () Segmentation fault (core dumped) If I run gdb on the kgdb.core file, it shows a corrupted - or at least massive - stack frame with no symbolic information. Is there a kgdb patch/update for 5.4 release p3 that I should apply? Or perhaps some permission/resource issue on the host that needs to be corrected? On Thursday 04 August 2005 06:10 pm, Marcel Moolenaar wrote: > On Aug 4, 2005, at 9:27 AM, Lonnie VanZandt wrote: > > Ok, so I infer that the startup sequence should be: > > > > 1. enter kdb on target > > 2. type gdb on target > > 3. type s on target > > 4. start kgdb on host with -r option > > 5. wait for good connection > > 6. load symbol table files on host > > 7. get on with the debugging > > > > Is this correct? > > Yes. > > > (There was not this requirement for strict ordering in the > > prior version of the remote protocol - or else it was at least more > > tolerant) > > I think the problem is that on the one hand the kernel sends a packet to > inform GDB that it has stopped and on the other hand GDB sends various > packets to figure out what the target is capable of. When this happens > at the same time, GDB gets confused. There has not been a change in KDB > and the GDB backend that makes this worse than before. It's all because > of a new version of GDB. > > FYI,