From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb@sourceware.org
Subject: Re: Small remote file transfer protocol adition
Date: Tue, 29 Jan 2008 13:58:00 -0000 [thread overview]
Message-ID: <20080129135832.GB22880@caradoc.them.org> (raw)
In-Reply-To: <479EAB6F.8040505@portugalmail.pt>
On Tue, Jan 29, 2008 at 04:28:31AM +0000, Pedro Alves wrote:
> To be able support this, this proposal adds an optional field
> to the reply packet:
>
> F$(retcode),$(remote_error),$(native_error);
I don't like designing an interface that is going to have to show hex
numbers to the user. They'd have to figure out that it was a target
error number and look it up themselves. Despite the localization
issues involved, do you think it might be better to add an error
string if you need the extra detail? We could put it in the
attachment field.
Could you give me an example of a useful error code which does not map
to one of the POSIX errors?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-29 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 4:29 Pedro Alves
2008-01-29 13:58 ` Daniel Jacobowitz [this message]
2008-01-29 15:21 ` Pedro Alves
2008-01-29 16:43 ` Daniel Jacobowitz
2008-01-29 17:52 ` Pedro Alves
2008-01-31 14:56 ` Daniel Jacobowitz
2008-01-31 18:15 ` 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=20080129135832.GB22880@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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