From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1364 invoked by alias); 20 Dec 2007 13:46:11 -0000 Received: (qmail 1346 invoked by uid 22791); 20 Dec 2007 13:46:06 -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; Thu, 20 Dec 2007 13:45:59 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 52C6F98151; Thu, 20 Dec 2007 13:45:57 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 24E6898150; Thu, 20 Dec 2007 13:45:57 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1J5Lim-0001ue-4o; Thu, 20 Dec 2007 08:45:56 -0500 Date: Thu, 20 Dec 2007 14:00:00 -0000 From: Daniel Jacobowitz To: Chris Demetriou Cc: gdb-patches@sources.redhat.com, Vladimir Prus Subject: Re: [RFA] 'set print thread-events' to control printing of thread start/exit messages Message-ID: <20071220134556.GA7244@caradoc.them.org> Mail-Followup-To: Chris Demetriou , gdb-patches@sources.redhat.com, Vladimir Prus References: <2e7be40c0712200003j29ca149hdd6e778f2aeec17a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2e7be40c0712200003j29ca149hdd6e778f2aeec17a@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-12-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: 2007-12/txt/msg00334.txt.bz2 On Thu, Dec 20, 2007 at 12:03:17AM -0800, Chris Demetriou wrote: > [hi! long time no see!] No kidding! > The attached patch makes the printing of thread start/exit messages on > Linux configurable via 'set print thread-events'. (A coworker > commented that for the benchmarks he was trying to debug, printing of > thread start/exit messages was ... quite tedious. And i figured a > patch would be ... quite straightforward.) > > I'm ambivalent about the name of the new option, and the location of > the option in the docs. I'm willing to listen to suggestions > (especially from approvers! 8-) of better alternatives. Hi Chris, meet Vladimir. Hi Vladimir, meet Chris. I suggest one of you combine this with Vladimir's recently pending patch to unify new thread printing in a single place for all targets. BTW, the new test would fail for GNU/Linux + gdbserver; that doesn't yet have any way to notify new threads, unlike the native support. -- Daniel Jacobowitz CodeSourcery