Re: inconsistent sigtramp code in mips target

Kevin Nomura
2003-10-29T22:43:04Z

On Wed, Oct 29, 2003 at 05:30:01PM -0500, Daniel Jacobowitz wrote:
> On Wed, Oct 29, 2003 at 05:27:40PM -0500, Andrew Cagney wrote:
> > >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.
>
> But since he's got a MIPS target, the frame sniffers won't help him at
> all, will they? They can't be used until the MIPS is converted.

Right. I used the new framework for i386, and am puzzling it out
for Alpha. MIPS is a horse of a different colour and required
breaking encapsulation entirely by hacking
frame.c:deprecated_update_frame_base_hack() in addition to the
above.