From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Report the main thread.
Date: Sun, 11 May 2008 16:00:00 -0000 [thread overview]
Message-ID: <200805111829.21105.vladimir@codesourcery.com> (raw)
In-Reply-To: <18470.65050.501601.790988@kahikatea.snap.net.nz>
On Sunday 11 May 2008 18:09:30 Nick Roberts wrote:
> > > Yes, you're right. I didn't notice that the observer in
> > > add_thread_with_info was removed at the same time this one was added.
> > >
> > > I just want threads other than the main thread to be reported, as used to
> > > be the case.
> >
> > Assuming that makes sense for annotations, I think your observer is in
> > position to decide which threads to report, and which not?
>
> Currently the new_thread observer only declares struct thread_info
What do you mean? The observer does not declare struct thread_info, it declares
a parameter having type 'struct thread_info'.
> and not it's
> members so I can't identify the thread number in annotate.c
struct thread_info is defined in gdbthread.h. What prevents you from including
that header?
> > > That way I can create a threads buffer and display the thread
> > > number when there is more than one thread.
> >
> > Cannot you just suppress display of thread list if there's just one
> > thread reported, on UI side?
>
> Yes, I could count the new-thread annotations and and only trigger things when
> there is more than one thread. It's simpler if I don't have to and I'm just
> baffled why I need to go through these hoops for a small stop gap change that
> no-one else is interested in using. The only requirement I can see on such a
> patch is that it doesn't affect anybody else's use of Gdb, and I think my
> original patch filled that requirement.
I have no opinion on this point (and I was not involved in the discussion of
your original patch).
- Volodya
next prev parent reply other threads:[~2008-05-11 14:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2008-04-30 10:11 ` Vladimir Prus
2008-04-30 13:28 ` Daniel Jacobowitz
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=200805111829.21105.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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