From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4681 invoked by alias); 14 Oct 2009 21:37:41 -0000 Received: (qmail 4672 invoked by uid 22791); 14 Oct 2009 21:37:40 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Oct 2009 21:37:36 +0000 Received: from list by lo.gmane.org with local (Exim 4.50) id 1MyBXK-0004wH-3h for gdb@sources.redhat.com; Wed, 14 Oct 2009 23:37:34 +0200 Received: from 82-68-48-14.dsl.in-addr.zen.co.uk ([82.68.48.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 23:37:34 +0200 Received: from jsmith by 82-68-48-14.dsl.in-addr.zen.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 23:37:34 +0200 To: gdb@sources.redhat.com From: Julian Smith Subject: Re: gdb displaying incorrect signal names with remote target ? Date: Thu, 15 Oct 2009 06:24:00 -0000 Message-ID: <20091014223706.abda80ec.jsmith@undo-software.com> References: <20091014214827.7259ea9e.jsmith@undo-software.com> <200910142204.58063.pedro@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00263.txt.bz2 On Wed, 14 Oct 2009 22:04:57 +0100 Pedro Alves wrote: > On Wednesday 14 October 2009 21:48:27, Julian Smith wrote: > > The inferior is receiving SIGUSR1 (signal number 10 on my i386 Linux > > system), thus the remote target sends a packet `S0a' to gdb. > > There's the problem. The remote target needs to send the > remote protocol code for SIGUSR1 , not the targets'. That would > be... TARGET_SIGNAL_USR1 = 30. The manual describes this: Ah, i completely missed that. Apolgies for the noise. Thanks (and to Daniel J also) - Julian > > "In the below the exact meaning of @dfn{signal > number} is defined by the header @file{include/gdb/signals.h} in the > @value{GDBN} source code." > > ... and include/gdb/signals.h says: > > /* The numbering of these signals is chosen to match traditional unix > signals (insofar as various unices use the same numbers, anyway). > It is also the numbering of the GDB remote protocol. Other remote > protocols, if they use a different numbering, should make sure to > translate appropriately. > > -- > Pedro Alves > -- http://undo-software.com/