This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: go32-nat, always a thread

From: Eli Zaretskii <eliz at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: pedro at codesourcery dot com, gdb-patches at sourceware dot org
Date: Fri, 08 Aug 2008 15:46:26 +0300
Subject: Re: go32-nat, always a thread
References: <200808080439.17254.pedro@codesourcery.com> <u3algj5qo.fsf@gnu.org> <20080808124229.GA23208@caradoc.them.org>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> 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?

Follow-Ups:
- Re: go32-nat, always a thread
  - From: Daniel Jacobowitz

References:
- go32-nat, always a thread
  - From: Pedro Alves
- Re: go32-nat, always a thread
  - From: Eli Zaretskii
- Re: go32-nat, always a thread
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]