From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20893 invoked by alias); 8 Aug 2008 12:55:17 -0000 Received: (qmail 20881 invoked by uid 22791); 8 Aug 2008 12:55:16 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Aug 2008 12:54:36 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id A4305983EF; Fri, 8 Aug 2008 12:54:34 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 873C69809F; Fri, 8 Aug 2008 12:54:34 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KRRUH-0006KM-OE; Fri, 08 Aug 2008 08:54:33 -0400 Date: Fri, 08 Aug 2008 12:55:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: pedro@codesourcery.com, gdb-patches@sourceware.org Subject: Re: go32-nat, always a thread Message-ID: <20080808125433.GA24230@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , pedro@codesourcery.com, gdb-patches@sourceware.org References: <200808080439.17254.pedro@codesourcery.com> <20080808124229.GA23208@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00195.txt.bz2 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 > > Cc: Pedro Alves , 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