From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23428 invoked by alias); 22 May 2012 10:58:19 -0000 Received: (qmail 23417 invoked by uid 22791); 22 May 2012 10:58:17 -0000 X-SWARE-Spam-Status: No, hits=-7.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 May 2012 10:58:03 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4MAvrK0031511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 May 2012 06:57:53 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4MAvp2R014563; Tue, 22 May 2012 06:57:52 -0400 Message-ID: <4FBB712F.2030604@redhat.com> Date: Tue, 22 May 2012 10:58:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Maciej W. Rozycki" CC: Michael Eager , "gdb-patches@sourceware.org" , Aleksandar Ristovski Subject: Re: MIPS Linux signals References: <4FB850CA.7090701@eagerm.com> <4FBAB500.7010104@redhat.com> <4FBAB948.7000808@eagerm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2012-05/txt/msg00813.txt.bz2 [Adding Aleksandar] Answering this one. On 05/21/2012 11:48 PM, Maciej W. Rozycki wrote: > Shall we drop the unused gdbarch API so as to avoid further confusion > then? If we don't find a use for it, yes. Aleksandar, we're discussing gdbarch_target_signal_from_host and gdbarch_target_signal_to_host. It turns out that uses to either of those were never added to GDB. gdbarch_target_signal_FROM_host's purpose is clear, and we're about to add a (new) use to fix the same situation you ran into at the time (cross core debugging). I'm wondering if you ever found a use for gdbarch_target_signal_TO_host that we should consider, though. -- Pedro Alves