From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23900 invoked by alias); 7 Nov 2007 04:59:13 -0000 Received: (qmail 23890 invoked by uid 22791); 7 Nov 2007 04:59:12 -0000 X-Spam-Check-By: sourceware.org Received: from omta03ps.mx.bigpond.com (HELO omta03ps.mx.bigpond.com) (144.140.82.155) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Nov 2007 04:59:09 +0000 Received: from oaamta03ps.mx.bigpond.com ([58.172.128.171]) by omta03ps.mx.bigpond.com with ESMTP id <20071107045905.WKHA25130.omta03ps.mx.bigpond.com@oaamta03ps.mx.bigpond.com> for ; Wed, 7 Nov 2007 04:59:05 +0000 Received: from kiwi.contemporary.net.au ([58.172.128.171]) by oaamta03ps.mx.bigpond.com with ESMTP id <20071107045900.DWSY21437.oaamta03ps.mx.bigpond.com@kiwi.contemporary.net.au> for ; Wed, 7 Nov 2007 04:59:00 +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 lA74wwnE019671 for ; Wed, 7 Nov 2007 15:58:59 +1100 Message-ID: <47314612.4060401@rtems.org> Date: Wed, 07 Nov 2007 04:59:00 -0000 From: Chris Johns User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: gdb-patches@sourceware.org Subject: Re: gdbserver pipe, xml and monitor changes References: <472FCE3E.8000508@rtems.org> <20071106033408.GA18729@caradoc.them.org> <47300364.3040000@rtems.org> <20071106125118.GA22174@caradoc.them.org> In-Reply-To: <20071106125118.GA22174@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/msg00107.txt.bz2 Daniel Jacobowitz wrote: > > This probably happens because GDB is careful about job control > (particularly tcsetpgrp) and gdbserver isn't. Or maybe it's because > oth are too careful about job control. > Ok. I will take a look. > This may be a rat's nest. If we can't get it to work, perhaps we > should restrict pipe to non-native targets. That would be a shame as the pipe option does allow you to have gdb run ssh and the gdbserver without anything special happening. Regards Chris