From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7482 invoked by alias); 26 Feb 2004 17:09:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7472 invoked from network); 26 Feb 2004 17:09:37 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 26 Feb 2004 17:09:37 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AwP0x-0002hy-TO; Thu, 26 Feb 2004 12:09:35 -0500 Date: Thu, 26 Feb 2004 17:09:00 -0000 From: Daniel Jacobowitz To: "Nathan J. Williams" Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] Gdbserver error codes Message-ID: <20040226170935.GA9354@nevyn.them.org> Mail-Followup-To: "Nathan J. Williams" , gdb-patches@sources.redhat.com References: <20040226151034.GA24170@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2004-02/txt/msg00764.txt.bz2 On Thu, Feb 26, 2004 at 12:08:08PM -0500, Nathan J. Williams wrote: > Daniel Jacobowitz writes: > > > Thanks to Eli for making me look closer at this. Parts of remote.c > > will reject ENN; in particular, ENN will cause remote_write_bytes to return > > an error but remote_read_bytes not to. Thus the 0xffffffff gdbserver has > > been printing instead of an error message for inaccessible memory regions. > > I still don't see that gdbserver will actually return an error if the > memory read fails; the target_ops read routine doesn't return an error > to the upper level, and the low transfer routines don't check the > ptrace return value and errno. I can put together my patches to > address this if there's interest. Oops, you're right. Of course there is interest - I'm always interested in fixes to gdbserver. Do you have or can you get a copyright assignment? > (while I'm at it, is there anything specifying that the hex format for > returned data is lowercase hex, or is the capital-E error return the only > implicit statement of that?) I have no idea. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer