From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24646 invoked by alias); 3 Sep 2009 02:50:55 -0000 Received: (qmail 24635 invoked by uid 22791); 3 Sep 2009 02:50:54 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Sep 2009 02:50:46 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n832ohBq020641; Wed, 2 Sep 2009 22:50:43 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n832ofcZ001308; Wed, 2 Sep 2009 22:50:41 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n832oeiD001975; Wed, 2 Sep 2009 22:50:40 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id D83A5378242; Wed, 2 Sep 2009 20:50:39 -0600 (MDT) From: Tom Tromey To: "Pierre Muller" Cc: Subject: Re: [RFC] Add possibility to stop at thread events References: <000301ca2be3$f534a8c0$df9dfa40$@u-strasbg.fr> Reply-To: tromey@redhat.com Date: Thu, 03 Sep 2009 02:50:00 -0000 In-Reply-To: <000301ca2be3$f534a8c0$df9dfa40$@u-strasbg.fr> (Pierre Muller's message of "Wed, 2 Sep 2009 17:42:20 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-09/txt/msg00076.txt.bz2 >>>>> "Pierre" == Pierre Muller writes: Pierre> The patch below adds the possibility to stop Pierre> the debuggee each time a thread is created or exited. Pierre> + add_setshow_zinteger_cmd ("stop-on-thread-events", class_support, Pierre> + &stop_on_thread_events, _("\ Did you consider making this a "catch" command instead? And consequently having it show up in "info break"? I think catch commands are preferable to other ad hoc "stopping" commands, because users can put commands on a catch, but they can't readily put commands on something like this. Tom