From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-17958-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 24909 invoked by alias); 28 Apr 2004 15:49:35 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 24848 invoked from network); 28 Apr 2004 15:49:33 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 28 Apr 2004 15:49:33 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i3SFnUKG025652
	for <gdb@sources.redhat.com>; Wed, 28 Apr 2004 11:49:30 -0400
Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i3SDiMv26465;
	Wed, 28 Apr 2004 09:44:22 -0400
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 1D79A2B9D; Wed, 28 Apr 2004 09:44:25 -0400 (EDT)
Message-ID: <408FB538.5060900@gnu.org>
Date: Wed, 28 Apr 2004 16:12:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217
MIME-Version: 1.0
To: David Daney <ddaney@avtrex.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: #1 0x1234456765432189 in <signal handler>
References: <40892F73.30209@gnu.org> <20040426111234.3eb8f0a5@saguaro> <408D66FF.1060004@avtrex.com>
In-Reply-To: <408D66FF.1060004@avtrex.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-04/txt/msg00176.txt.bz2

> Kevin Buettner wrote:
> 
>> On Fri, 23 Apr 2004 11:00:03 -0400
>> Andrew Cagney <cagney@gnu.org> wrote:
>>
>>  
>>
>>> At present a signal handler, in a backtrace is displayed as:
>>>
>>> #0  catcher (signal=26) at /home/cygnus/cagney/GDB/src/gdb/testsuite/gdb.base/sigaltstack.c:71
>>> #1  <signal handler called>
>>> #2  0x0000000000400751 in thrower (next_level=INNER, sig=26, itimer=1, on_stack=134217728) at /home/cygnus/cagney/GD
>>>
>>> It isn't exactly informative.  Since we're now expecting GDB to do something sane with a signal handlers, I think how it is displayed should be changed.  In particular the output should be changed to:
>>>
>>> #1  0xffff01111111 in <signal handler>
>>>
>>> thoughts?
>>>   
>>
>>
>> I have no objection to printing an address, but I don't think
>> that referring to the thing in frame #1 as "<signal handler>"
>> is correct.  The signal handler in this case is actually catcher().
>> Frame #1 is created by the OS to hold the process's state prior to
>> receiving the signal in question.

Right, however

 >> That being the case, I'd like to
>> see either:
>>
>> #1  0xffff01111111 in <signal handler caller>
>>
>> or:
>>
>> #1  0xffff01111111 in <signal context frame>

on this mailing list, we refer to it as:

	#1 0x1234 in <signal trampoline>

so we might as well be consistent and use that.

>>
> There are typically several other things that are known about the signal at this point.  How about adding signal number (or name), cause, faulting address, etc.

A thing to look at one day is per-frame "info frame" information.

Andrew