From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix uninitialized use of variables.
Date: Wed, 24 Oct 2007 17:12:00 -0000 [thread overview]
Message-ID: <m3y7dstq00.fsf@codesourcery.com> (raw)
In-Reply-To: <20071024001018.GA15419@caradoc.them.org> (Daniel Jacobowitz's message of "Tue, 23 Oct 2007 20:10:18 -0400")
Daniel Jacobowitz <dan at codesourcery.com> writes:
> On Tue, Oct 23, 2007 at 04:20:12PM -0700, Jim Blandy wrote:
>> This looks fine to me, although Daniel has thoughts on error handling
>> in the remote protocol that I don't fully understand.
>
> Nothing recent or complicated. I just want it to become more
> consistent rather than less...
Here's what I was thinking of:
http://sourceware.org/ml/gdb-patches/2007-07/msg00071.html
From: Daniel Jacobowitz
I would like for us to unify the error handling in the remote target
along with this. It's very jumbled as to what's a warning and what
isn't.
I think I also remember you expressing concern about throwing 'error'
during the connection process.
Can you fill us in more on how you'd like remote.c to work? Maybe we
can get started, and even get those textual error messages in.
next prev parent reply other threads:[~2007-10-24 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 18:07 Carlos O'Donell
2007-10-23 23:20 ` Jim Blandy
2007-10-24 17:24 ` Carlos O'Donell
2007-10-24 0:10 ` Jim Blandy
2007-10-24 4:05 ` Daniel Jacobowitz
2007-10-24 17:12 ` Jim Blandy [this message]
2007-10-24 17:57 ` Daniel Jacobowitz
2007-10-24 17:15 ` Jim Blandy
2007-10-24 18:02 ` Carlos O'Donell
2007-10-24 18:21 ` Jim Blandy
2007-10-26 18:51 ` Carlos O'Donell
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=m3y7dstq00.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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