This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Implement thread death notification.
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: Nick Roberts <nickrob at snap dot net dot nz>
- Cc: "gdb-patches at sources"@redhat.com
- Date: Tue, 29 Apr 2008 22:16:45 +0400
- Subject: Re: [RFA] Implement thread death notification.
- References: <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