From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] small change for better error reporting in remote.c
Date: Fri, 31 Jul 2009 21:43:00 -0000 [thread overview]
Message-ID: <20090731205526.GA29107@caradoc.them.org> (raw)
In-Reply-To: <4A735491.4040006@vmware.com>
On Fri, Jul 31, 2009 at 01:31:13PM -0700, Michael Snyder wrote:
> You may not realize it, but you're asking for a much bigger change.
> There is no struct packet_config for the 'G' packet. I'll have to
> change set_registers_using_G from void to int, so that it can
> return failure if the 'G' packet is unsupported.
>
> But I'll begin working on it, unles I hear "never mind"
> from you... ;-)
Bah... no, don't bother with that. What I actually wanted is
just packet_check_result. Is that easier? :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-07-31 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 0:41 Michael Snyder
2009-07-31 9:00 ` drow
2009-07-31 21:00 ` Michael Snyder
2009-07-31 21:43 ` Daniel Jacobowitz [this message]
2009-07-31 22:13 ` Michael Snyder
2009-07-31 22:09 ` Pedro Alves
2009-07-31 22:15 ` Michael Snyder
2009-07-31 22:49 ` Pedro Alves
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=20090731205526.GA29107@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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