From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: nickrob@snap.net.nz, vladimir@codesourcery.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Report the main thread.
Date: Sun, 27 Apr 2008 18:25:00 -0000 [thread overview]
Message-ID: <20080427153421.GA14695@caradoc.them.org> (raw)
In-Reply-To: <200804271422.m3REMxVF009472@brahms.sibelius.xs4all.nl>
On Sun, Apr 27, 2008 at 04:22:59PM +0200, Mark Kettenis wrote:
> Seriously though, in GDB we've always only populated the threads list
> if a program actually has threads. An MI client will have to deal
> with that fact. If it insists on providing a threaded view of the
> world, it needs to fake up a main thread. Since it already has to do
> that for non-threaded programs, why would having a false thread create
> event for the main thread help?
Personally I think that's a mistake. And if we don't want to change
the remaining backends - some of them already populated the first
thread, IIRC, and Linux now does - then maybe we should change MI
to fake up the thread. It seems like a silly thing to make each
client do individually.
The "always a frame" work has made parts of GDB much clearer; I think
"always a thread" would too. The big win would be exactly what Pedro
mentioned - it would simplify execution control.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-27 15:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 16:44 Vladimir Prus
2008-04-26 17:16 ` Mark Kettenis
2008-04-26 17:22 ` Daniel Jacobowitz
2008-04-26 17:31 ` Vladimir Prus
2008-04-26 21:05 ` Daniel Jacobowitz
2008-04-26 22:36 ` Vladimir Prus
2008-04-27 4:27 ` Nick Roberts
2008-04-27 9:03 ` Vladimir Prus
2008-04-27 11:14 ` Daniel Jacobowitz
2008-04-27 14:24 ` Nick Roberts
2008-04-27 13:53 ` Nick Roberts
2008-04-27 15:50 ` Daniel Jacobowitz
2008-04-27 16:07 ` Mark Kettenis
2008-04-27 16:07 ` Pedro Alves
2008-04-27 21:46 ` Mark Kettenis
2008-04-28 3:31 ` Pedro Alves
2008-04-27 18:25 ` Daniel Jacobowitz [this message]
2008-04-30 10:11 ` Vladimir Prus
2008-04-30 13:28 ` Daniel Jacobowitz
2008-05-10 18:00 Nick Roberts
2008-05-10 19:26 ` Vladimir Prus
2008-05-11 14:10 ` Nick Roberts
2008-05-11 14:45 ` Vladimir Prus
2008-05-11 15:52 ` Nick Roberts
2008-05-11 16:00 ` Vladimir Prus
2008-05-11 16:13 ` Nick Roberts
2008-05-11 16:41 ` Vladimir Prus
2008-05-11 22:19 ` Nick Roberts
2008-05-12 22:22 ` Michael Snyder
2008-05-11 20:19 ` Joel Brobecker
2008-05-11 21:10 ` Vladimir Prus
2008-05-11 22:33 ` Nick Roberts
2008-05-12 3:18 ` Daniel Jacobowitz
2008-05-12 16:11 ` Nick Roberts
2008-05-12 18:19 ` Daniel Jacobowitz
2008-05-10 19:42 ` Vladimir Prus
2008-05-10 22:12 ` Joel Brobecker
2008-05-11 14:29 ` Nick Roberts
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=20080427153421.GA14695@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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