Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Masaki MURANAKA <monaka@monami-software.com>,
		gdb-patches@sourceware.org
Subject: Re: Signal definitions for host=mingw32/target=*-*-*
Date: Sat, 15 Apr 2006 18:42:00 -0000	[thread overview]
Message-ID: <20060415184247.GA10060@nevyn.them.org> (raw)
In-Reply-To: <uwtdqzofy.fsf@gnu.org>

On Sat, Apr 15, 2006 at 09:25:05PM +0300, Eli Zaretskii wrote:
> > Index: gdb/remote-sim.c
> > ===================================================================
> > RCS file: /home/cvs/pizzafactory/gdb/gdb/remote-sim.c,v
> > retrieving revision 1.4
> > diff -r1.4 remote-sim.c
> > 46a47,58

Masaki MURANAKA wrote that this patch was against GDB 6.4.  Please
try HEAD instead.

> Btw, I don't see these signals used anywhere in remote-sim.c.  Why did
> you need to add them?

They used to be, until:

revision 1.50
date: 2005/11/28 18:32:32;  author: mmitchel;  state: Exp;  lines: +6 -11
        * remote-sim.c (gdbsim_wait): Pass target signal numbers to
        sim_resume.  Expect target signal numbers from sim_stop_reason.

There's still uses of sim_signal_to_host in the simulator, but I don't
quite understand most of them.  I think they're all buggy.  I went
over Mark's patch carefully at the time, but now I see the result of
sim_signal_to_host being compared against signals from sim_stop_reason,
which uses sim_signal_to_target...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-15 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15 16:36 Masaki MURANAKA
2006-04-15 18:25 ` Eli Zaretskii
2006-04-15 18:42   ` Daniel Jacobowitz [this message]
2006-04-16  1:17     ` Masaki MURANAKA
2006-04-16  6:05     ` Eli Zaretskii
2006-04-16 15:54       ` Daniel Jacobowitz

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=20060415184247.GA10060@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.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