From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Using bt command in async mode
Date: Thu, 10 Apr 2008 15:36:00 -0000 [thread overview]
Message-ID: <m3iqypohtv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080410142029.GB21662@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 10 Apr 2008 10\:20\:29 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> Seems like this will be just as awkward in the long term, but
Daniel> it's an improvement.
Is there some other approach you'd prefer?
Daniel> OK if it tested fine.
I didn't run the test suite without the patch; I'll do that next week
& check it in if it looks ok.
Tom
next prev parent reply other threads:[~2008-04-10 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 2:08 Nick Roberts
2008-04-01 19:55 ` Tom Tromey
2008-04-01 22:30 ` Nick Roberts
2008-04-10 16:05 ` Vladimir Prus
2008-04-11 22:55 ` Nick Roberts
2008-04-10 15:22 ` Daniel Jacobowitz
2008-04-10 15:36 ` Tom Tromey [this message]
2008-04-10 15:39 ` Pedro Alves
2008-04-17 2:58 ` Tom Tromey
2008-04-10 15:53 ` Daniel Jacobowitz
2008-04-17 2:47 ` Tom Tromey
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=m3iqypohtv.fsf@fleche.redhat.com \
--to=tromey@redhat.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