Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
	       "'GDB Patches'" <gdb-patches@sourceware.org>
Subject: Re: [RFC/PATCH] Add new internal variable $_signo
Date: Sat, 15 Jun 2013 06:46:00 -0000	[thread overview]
Message-ID: <m3vc5gwhue.fsf@redhat.com> (raw)
In-Reply-To: <51BB7B58.9030007@redhat.com> (Pedro Alves's message of "Fri, 14	Jun 2013 21:21:44 +0100")

On Friday, June 14 2013, Pedro Alves wrote:

> gdb_signal_to_host is the fallback (and having a fallback is sort of a
> hack).  The right signal number is the target's not the host's.  We
> have gdbarch_gdb_signal_from_target for the opposite direction, but not
> gdbarch_gdb_signal_to_target...  Having to bake the target OS's signal
> numbers into GDB is a bit unfortunate, though we could get around it
> at some point if we wanted by extending the RSP, and/or adding a python
> hook.

I was looking for a target variant but found none.  I'm not sure what
you mean with your comment.  Are you suggesting that I take care of this
as well?

In the meantime, I will leave the code as-is, i.e., without doing any
kind of conversion on infrun.c

-- 
Sergio


  reply	other threads:[~2013-06-14 20:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  2:39 Sergio Durigan Junior
2013-06-14  7:49 ` Eli Zaretskii
2013-06-16  6:08   ` Sergio Durigan Junior
2013-06-14  8:59 ` Mark Kettenis
2013-06-14  9:37 ` Pierre Muller
2013-06-14 17:59   ` Sergio Durigan Junior
2013-06-14 20:36     ` Pedro Alves
2013-06-15  6:46       ` Sergio Durigan Junior [this message]
2013-06-17 17:02         ` Pedro Alves
2013-06-14 17:58 ` Pedro Alves
2013-06-16  5:57   ` Sergio Durigan Junior
2013-06-16  6:25     ` Sergio Durigan Junior
2013-06-17 17:20     ` Pedro Alves
2013-07-17 18:41 ` Tom Tromey

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=m3vc5gwhue.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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