Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Michael Eager <eager@eagerm.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       Aleksandar Ristovski <aristovski@qnx.com>
Subject: Re: MIPS Linux signals
Date: Tue, 22 May 2012 10:58:00 -0000	[thread overview]
Message-ID: <4FBB712F.2030604@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1205212340180.11227@tp.orcam.me.uk>

[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


  parent reply	other threads:[~2012-05-22 10:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20  2:03 Michael Eager
2012-05-21 11:04 ` Pedro Alves
2012-05-21 14:51   ` Michael Eager
2012-05-21 17:37     ` Pedro Alves
2012-05-21 18:06       ` Michael Eager
2012-05-21 18:19 ` Maciej W. Rozycki
     [not found] ` <alpine.DEB.1.10.1205211232260.11227@tp.orcam.me.uk>
2012-05-21 18:21   ` Michael Eager
2012-05-21 22:34     ` Maciej W. Rozycki
2012-05-22  9:38       ` Pedro Alves
2012-05-21 21:35 ` Pedro Alves
2012-05-21 21:53   ` Michael Eager
2012-05-21 22:48     ` Maciej W. Rozycki
2012-05-22  0:16       ` Michael Eager
2012-05-22 10:17       ` Pedro Alves
2012-05-22 13:16         ` Maciej W. Rozycki
2012-05-22 13:32           ` Pedro Alves
2012-05-22 15:10         ` Move store_waitstatus to inf-child.c (was: Re: MIPS Linux signals) Pedro Alves
2012-05-22 15:40         ` MIPS Linux signals Michael Eager
2012-05-22 16:02           ` Pedro Alves
2012-05-22 18:14             ` Michael Eager
2012-05-22 18:31               ` Pedro Alves
2012-05-22 19:32                 ` Michael Eager
2012-05-22 22:06                   ` Pedro Alves
2012-05-22 16:26         ` Pedro Alves
2012-05-22 10:58       ` Pedro Alves [this message]
2012-05-22 19:31         ` Aleksandar Ristovski
2012-05-22 21:55           ` Pedro Alves
2012-05-22 23:29             ` Aleksandar Ristovski
2012-05-23 11:39               ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FBB712F.2030604@redhat.com \
    --to=palves@redhat.com \
    --cc=aristovski@qnx.com \
    --cc=eager@eagerm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox