From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30053 invoked by alias); 16 Nov 2012 08:25:25 -0000 Received: (qmail 30030 invoked by uid 22791); 16 Nov 2012 08:25:18 -0000 X-SWARE-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Nov 2012 08:25:12 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MDK00200MSN1N00@a-mtaout21.012.net.il> for gdb@sourceware.org; Fri, 16 Nov 2012 10:25:10 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MDK002VUNDY1330@a-mtaout21.012.net.il>; Fri, 16 Nov 2012 10:25:10 +0200 (IST) Date: Fri, 16 Nov 2012 08:25:00 -0000 From: Eli Zaretskii Subject: Re: Time to expand "Program received signal" ? In-reply-to: To: Paul_Koning@Dell.com Cc: gnu@toad.com, tromey@redhat.com, palves@redhat.com, mark.kettenis@xs4all.nl, brobecker@adacore.com, gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: <83r4nurm46.fsf@gnu.org> References: <50A13A4E.3020000@redhat.com> <20121113162530.GX4847@adacore.com> <201211131640.qADGeKhs021376@glazunov.sibelius.xs4all.nl> <50A281BC.9030802@redhat.com> <201211132240.qADMeB2N032392@new.toad.com> <871ufu1zyx.fsf@fleche.redhat.com> <201211152221.qAFML62N024464@new.toad.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00052.txt.bz2 > From: > CC: , , , , > Date: Thu, 15 Nov 2012 22:26:27 +0000 > > But you didn't address the issue that you can't readily tell whether a program is multi-threaded. It may have had multiple threads but it doesn't now, or it may have more later. At least on MS-Windows, GDB tells me when a new thread is created. So it does know. I have no experience with threads on Posix platforms, so I don't know for sure that the same is possible there. But the "set print thread-events" command is not Windows-specific, so I believe the above is also true for Posix platforms.