From: Jason Molenda <jason-swarelist@molenda.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC a little redundancy removal I'd like in gdb.mi
Date: Thu, 10 Oct 2002 16:09:00 -0000 [thread overview]
Message-ID: <20021010160743.A38140@molenda.com> (raw)
In-Reply-To: <20021010160547.A36555@molenda.com>; from jason-swarelist@molenda.com on Thu, Oct 10, 2002 at 04:05:47PM -0700
On Thu, Oct 10, 2002 at 04:05:47PM -0700, Jason Molenda wrote:
> Problems with my change include
>
> mi_get_stopped doesn't look for a specific result code, just the *stopped
> message.
(I mean "specific sequence #" - it'll accept any old sequence number. This
doesn't concern me overly; if the sequence number stuff was broken I imagine
that'll be readily apparent from all the other tests.)
next prev parent reply other threads:[~2002-10-10 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 16:07 Jason Molenda
2002-10-10 16:09 ` Jason Molenda [this message]
2002-10-18 15:11 ` Elena Zannoni
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=20021010160743.A38140@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=gdb-patches@sources.redhat.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