From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-41524-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 15993 invoked by alias); 14 Nov 2012 19:54:43 -0000
Received: (qmail 15983 invoked by uid 22791); 14 Nov 2012 19:54:41 -0000
X-SWARE-Spam-Status: No, hits=0.5 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_BRBL_LASTEXT,RCVD_IN_HOSTKARMA_YE,RCVD_IN_MSPIKE_BL,RCVD_IN_MSPIKE_L3,RCVD_IN_NJABL_RELAY,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from new.toad.com (HELO new.toad.com) (209.237.225.253)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Nov 2012 19:54:34 +0000
Received: from new.toad.com (localhost.localdomain [127.0.0.1])	by new.toad.com (8.12.9/8.12.9) with ESMTP id qAEJsQ2N026469;	Wed, 14 Nov 2012 11:54:26 -0800
Message-Id: <201211141954.qAEJsQ2N026469@new.toad.com>
To: Pedro Alves <palves@redhat.com>
cc: John Gilmore <gnu@toad.com>, Mark Kettenis <mark.kettenis@xs4all.nl>,   brobecker@adacore.com, gdb@sourceware.org
Subject: Re: Time to expand "Program received signal" ?
In-reply-to: <50A371C6.3080307@redhat.com>
References: <50A13A4E.3020000@redhat.com> <20121113162530.GX4847@adacore.com> <201211131640.qADGeKhs021376@glazunov.sibelius.xs4all.nl> <50A281BC.9030802@redhat.com> <201211132240.qADMeB2N032392@new.toad.com> <50A371C6.3080307@redhat.com>
Comments: In-reply-to Pedro Alves <palves@redhat.com>   message dated "Wed, 14 Nov 2012 10:26:14 +0000."
Date: Wed, 14 Nov 2012 19:54:00 -0000
From: John Gilmore <gnu@toad.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2012-11/txt/msg00029.txt.bz2

> > GDB shouldn't mention threads at all, unless the program being debugged
> > is multi-threaded.
> 
> Since 7.0 GDB models non-threaded programs as single threaded.

OK, then, you can call it what you want.  GDB shouldn't mention
threads at all, unless the program being debugged has more than a
single thread.

Printing a thread identifier is extraneous information that the user
will just have to skip over to get to the real information (that their
program got a signal).

	John