From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4135 invoked by alias); 6 Nov 2007 06:02:22 -0000 Received: (qmail 4124 invoked by uid 22791); 6 Nov 2007 06:02:21 -0000 X-Spam-Check-By: sourceware.org Received: from omta03sl.mx.bigpond.com (HELO omta03sl.mx.bigpond.com) (144.140.92.155) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Nov 2007 06:02:18 +0000 Received: from oaamta04sl.mx.bigpond.com ([58.172.128.171]) by omta03sl.mx.bigpond.com with ESMTP id <20071106060214.ZKGS4366.omta03sl.mx.bigpond.com@oaamta04sl.mx.bigpond.com> for ; Tue, 6 Nov 2007 06:02:14 +0000 Received: from kiwi.contemporary.net.au ([58.172.128.171]) by oaamta04sl.mx.bigpond.com with ESMTP id <20071106060213.RWNT19591.oaamta04sl.mx.bigpond.com@kiwi.contemporary.net.au>; Tue, 6 Nov 2007 06:02:13 +0000 Received: from [172.16.100.190] (moa.contemporary.net.au [172.16.100.190]) by kiwi.contemporary.net.au (8.14.1/8.14.1) with ESMTP id lA662CxN007631; Tue, 6 Nov 2007 17:02:13 +1100 Message-ID: <47300364.3040000@rtems.org> Date: Tue, 06 Nov 2007 06:02:00 -0000 From: Chris Johns User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Chris Johns , gdb-patches@sourceware.org Subject: Re: gdbserver pipe, xml and monitor changes References: <472FCE3E.8000508@rtems.org> <20071106033408.GA18729@caradoc.them.org> In-Reply-To: <20071106033408.GA18729@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-11/txt/msg00090.txt.bz2 Daniel Jacobowitz wrote: > > Take a look at the gdb Wiki; there's a page describing how to run the > testsuite against a local gdbserver. Great. This is what I was after. I only have the x86 Linux option to test. > First of all, do you have a copyright assignment? This is too big to > take without one. I see something that looks like you in the > copyright assignment list, but the associated employer disclaimer is > expired. That is me. I will contact the FSF and get this updated. > > After that's taken care of, I'd really appreciate it if you could > break this up into a couple of logical pieces. It makes them a lot > easier to look at. For instance, the register shadow cache is > independent of everything else. > Sure that is no problem. > The pipe changes are user-visible, so we should update the manual. I > can take care of that later. I did notice the documentation and I am fine with getting that in-order. > >> The various low level back-ends have not be changed to printf_filtered or >> warning. Should they ? > > Yes, if we document that pipe is available for them. > Ok. Using the pipe mode to run the linux gdbserver resulted in gdb being suspended. I suspect a signal was passed up. It did not show up with the BDM back-end because the target is not Unix process. Any ideas where I look ? Regards Chris