Date: Mon, 3 Dec 2007 21:46:16 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: Julian Elischer <julian@elischer.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: remote gdb failures in recent builds (last 6 months or so.) Message-ID: <E907A5BE-297F-4B62-9BBC-252EF630B110@mac.com> In-Reply-To: <4754E54C.20104@elischer.org> References: <4754D411.6060608@elischer.org> <A3A1F0CB-CF92-4D42-8211-241A561D2130@mac.com> <4754E54C.20104@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E907A5BE-297F-4B62-9BBC-252EF630B110>