Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "gdb-patches@sources"@redhat.com
Subject: Re: [RFA] Implement thread death notification.
Date: Tue, 29 Apr 2008 20:07:00 -0000	[thread overview]
Message-ID: <200804292216.45231.vladimir@codesourcery.com> (raw)
In-Reply-To: <18452.16686.528039.84732@kahikatea.snap.net.nz>

On Sunday 27 April 2008 13:02:38 Nick Roberts wrote:
> 
> > We now have the 'thread-created' MI notification. This patch adds a
> > 'thread-exited' notification to match. Are non-MI bits of this
> > patch OK?
> 
> When I suggested this previously, we said:
> 
> > > I'm not sure what you mean.  If I run Gdb normally with a multi-threaded
> > > application, I get:
> > > 
> > > [New Thread -1210639472 (LWP 7235)]
> > > 
> > > when a thread is created and:
> > > 
> > > [Thread -1210639472 (LWP 7235) exited]
> > > 
> > > when it is terminated.
> >
> > At which point, and where in code is that message printed? It is
> > printed by linux-thread-db.c:detach_thread, so it's not good for
> > generic code. And generic code will hold on to thread until 
> > "info thread". It's not very good if you need to issue "info thread"
> > to get notifications about exited thread.
> > 
> > So, thread.c and its interaction with linux-thread-db.c have to
> > be fixed.
> 
> Does it mean that this has now been fixed?

No. However, it seems useful to provide this notification initially for Linux.

- Volodya


  reply	other threads:[~2008-04-29 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 15:03 Nick Roberts
2008-04-29 20:07 ` Vladimir Prus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-26 17:45 Vladimir Prus
2008-05-01 20:04 ` Daniel Jacobowitz
2008-05-01 20:13   ` Vladimir Prus
2008-05-01 20:21     ` 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=200804292216.45231.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