Re: go32-nat, always a thread

[Daniel Jacobowitz <drow@false.org>]

On Fri, Aug 08, 2008 at 03:46:26PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 8 Aug 2008 08:42:29 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
> > 
> > > The code you added will now cause all kinds of notifications, like
> > > "thread started", be displayed, which is just confusing when the
> > > programmer knows there're no threads.  Is this really justified?
> > 
> > No notifications should be displayed; that's because Pedro used
> > add_thread_silent and delete_thread_silent.
> 
> Then what do the calls to observer_notify_new_thread and its ilk do?

They allow parts of GDB to respond to changes in the thread list.  The
user-visible notification isn't handled from there, but the MI front
end notification is; we decided (after a lot of discussion...) that
this is the desirable behavior, for the same reason it's useful in GDB
to always have at least one thread while the program is running.

-- 
Daniel Jacobowitz
CodeSourcery