[RFC] Non-executable stack on SPARC

Daniel Jacobowitz drow@mvista.com
Sun Jan 25 23:59:00 GMT 2004


On Mon, Jan 26, 2004 at 12:50:11AM +0100, Mark Kettenis wrote:
> A while ago, I established that getting inferior function calls on
> SPARC working with a non-executable stack is remarkably simple.  Just
> acknowledging that breakpoint instructions may cause SIGSEGV, as per
> the attached patch, is enough.  However, some people were afraid that
> blindly applying this patch might cause some problems on other
> targets.  I think there are two alternatives:
> 
> 1. Only check for SIGSEGV if the target in question uses "ON_STACK"
>    for its call_dummy_location.
> 
> 2. Add a new method to the architecture vector to check whether a
>    particular signal may have been the result of a breakpoint
>    instruction.  Suggested name & signature:
> 
>    int breakpoint_signal_p (struct gdbarch *gdbarch, int signal)
> 
> Preferences?

I think just the patch you included will be OK.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



More information about the Gdb mailing list