This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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'd like to get this sorted before 6.1, since OpenBSD/sparc has a non-executable stack, and some people are running SPARC Solaris with a non-executable stack too.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |