From owner-freebsd-current@FreeBSD.ORG Tue Dec 4 05:46:36 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A51016A41A for ; Tue, 4 Dec 2007 05:46:36 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.83]) by mx1.freebsd.org (Postfix) with ESMTP id 9186E13C44B for ; Tue, 4 Dec 2007 05:46:36 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp006-s [10.150.69.69]) by smtpoutm.mac.com (Xserve/smtpout020/MantshX 4.0) with ESMTP id lB45kZPN007941; Mon, 3 Dec 2007 21:46:35 -0800 (PST) Received: from [192.168.1.100] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/asmtp006/MantshX 4.0) with ESMTP id lB45kOxP008899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 3 Dec 2007 21:46:33 -0800 (PST) Message-Id: From: Marcel Moolenaar To: Julian Elischer In-Reply-To: <4754E54C.20104@elischer.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Mon, 3 Dec 2007 21:46:16 -0800 References: <4754D411.6060608@elischer.org> <4754E54C.20104@elischer.org> X-Mailer: Apple Mail (2.915) Cc: FreeBSD Current Subject: Re: remote gdb failures in recent builds (last 6 months or so.) 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: Tue, 04 Dec 2007 05:46:36 -0000 On Dec 3, 2007, at 9:27 PM, Julian Elischer wrote: > It's slowly been getting worse (across many pairs of machines) over > the last few years. finally today it just doesn't work at all. I've > used this pair of machines many times before. usually it takes > "luck" to get synced up but once it's synced, it's solid. How do you start the connection? I seem to recall that starting with the gdb client is not a good idea, because the gdb client will try a couple of commands first to see if the stub supports them. If the stub is not ready, then the gdb client may think the stub is not capable of certain features. I typically have the kernel break into the GDB debugger first and then I start the gdb client... -- Marcel Moolenaar xcllnt@mac.com