From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Signal definitions for host=mingw32/target=*-*-*
Date: Sun, 16 Apr 2006 15:54:00 -0000 [thread overview]
Message-ID: <20060416155425.GA25863@nevyn.them.org> (raw)
In-Reply-To: <uu08uys0w.fsf@gnu.org>
On Sun, Apr 16, 2006 at 09:05:19AM +0300, Eli Zaretskii wrote:
> > Date: Sat, 15 Apr 2006 14:42:47 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Masaki MURANAKA <monaka@monami-software.com>,
> > gdb-patches@sourceware.org
> >
> > 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, I'm not sure what you are saying. Are you saying that Mark's
> patch was wrong in that it introduced bugs that were not there before?
Since the host and target signal numberings in these ranges are exactly
the same, no. It simply failed to fix some bugs which were previously
present when signals are missing.
The remaining calls to sim_signal_to_host should be looked at
carefully; that is the correct fix for this problem.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-04-16 15:54 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
2006-04-16 1:17 ` Masaki MURANAKA
2006-04-16 6:05 ` Eli Zaretskii
2006-04-16 15:54 ` Daniel Jacobowitz [this message]
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=20060416155425.GA25863@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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