Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Nathan J. Williams" <nathanw@wasabisystems.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [patch] Gdbserver error codes
Date: Thu, 26 Feb 2004 17:41:00 -0000	[thread overview]
Message-ID: <403E2FCE.6090607@gnu.org> (raw)
In-Reply-To: <20040226170935.GA9354@nevyn.them.org>

> On Thu, Feb 26, 2004 at 12:08:08PM -0500, Nathan J. Williams wrote:
> 
>>> Daniel Jacobowitz <drow@false.org> 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?

Wasabi have a blanket 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.

In general?  Assume its lowercase.  No, it probably isn't explicit.

Andrew




      parent reply	other threads:[~2004-02-26 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 15:10 Daniel Jacobowitz
2004-02-26 17:08 ` Nathan J. Williams
2004-02-26 17:09   ` Daniel Jacobowitz
2004-02-26 17:16     ` Nathan J. Williams
2004-02-26 17:41     ` Andrew Cagney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=403E2FCE.6090607@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nathanw@wasabisystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox