From: Jim Blandy <jimb@codesourcery.com>
To: Pawel Piech <pawel.piech@windriver.com>
Cc: gdb@sourceware.org
Subject: Re: Non-stop multi-threaded debugging
Date: Tue, 04 Dec 2007 18:34:00 -0000 [thread overview]
Message-ID: <m3hciyfgx1.fsf@codesourcery.com> (raw)
In-Reply-To: <474CFA34.1030309@windriver.com> (Pawel Piech's message of "Tue, 27 Nov 2007 21:18:44 -0800")
Folks should treat this post:
http://sourceware.org/ml/gdb/2007-11/msg00198.html
as an attempt to mention all the relevant issues --- not as a fully
worked-out design. The plan was to hash out the details through
discussion amongst the front end authors on this list. I don't have
experience writing clients for MI; I've only dealt with implementing
it in GDB, and even then not much. So you people who work on
real-life front ends are in a much better position to see what would
work best.
So I encourage you, Vlad, Nick, and the rest of the MI fans to hash it
all out and come up with something everyone is satisfied with. We
just need to make sure that the issues the analysis raises all get
addressed (or dismissed).
next prev parent reply other threads:[~2007-12-04 18:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 5:18 Pawel Piech
2007-11-29 2:08 ` Nick Roberts
2007-11-29 6:15 ` Pawel Piech
2007-11-29 6:46 ` gdb over RNDIS to PDA Steve DeLaney
2007-11-29 8:36 ` Non-stop multi-threaded debugging Vladimir Prus
2007-11-29 16:42 ` Pawel Piech
[not found] ` <474EEB36.1040203@windriver.com>
2007-11-29 16:46 ` Vladimir Prus
2007-11-29 17:36 ` Pawel Piech
2007-11-29 17:51 ` Vladimir Prus
2007-11-29 18:13 ` Pawel Piech
2007-12-04 18:34 ` Jim Blandy [this message]
2007-12-04 23:05 ` Pawel Piech
2007-12-05 21:52 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2007-11-20 17:21 Nathan Sidwell
2007-11-20 19:28 ` Nick Roberts
2007-11-20 20:12 ` Jim Blandy
2007-11-21 13:53 ` Michael Snyder
2007-11-26 23:13 ` Jim Blandy
2007-11-27 16:42 ` Ulrich Weigand
2007-11-30 20:48 ` Thiago Jung Bauermann
2007-12-04 18:17 ` Jim Blandy
2007-12-05 13:41 ` Fabian Cenedese
2007-12-05 20:01 ` Nigel Stephens
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=m3hciyfgx1.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=pawel.piech@windriver.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