From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Nomura <nomura@netapp.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: inconsistent sigtramp code in mips target
Date: Wed, 29 Oct 2003 22:27:00 -0000 [thread overview]
Message-ID: <3FA03EDC.2090407@redhat.com> (raw)
In-Reply-To: <20031028215814.GY4320@bughouse.netapp.com>
> The logical patch would be to move the special cases up front,
> but I have no way to test this out (no access to a MIPS UNIX
> platform).
>
> On the other hand this isn't purely academic. I came across this
> because I need to define a custom sigtramp frame for our own
> MIPS embedded platform. It was baffling for a while that my
> modification to the SP_REGNUM override had no effect.
Rather than the MIPS, check the x86 family for how to add a custom
sigtramp handler (ex, i386_sigtramp_frame_sniffer). Hopefully the new
mechanism is less baffling - the current MIPS code is not a good reference.
Andrew
next prev parent reply other threads:[~2003-10-29 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 21:58 Kevin Nomura
2003-10-29 22:27 ` Andrew Cagney [this message]
2003-10-29 22:30 ` Daniel Jacobowitz
2003-10-29 22:43 ` Kevin Nomura
2003-10-29 22:50 ` Andrew Cagney
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=3FA03EDC.2090407@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nomura@netapp.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