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]

Re: [RFC] Non-executable stack on SPARC


Assuming that for VLIW gdb replaces the entire instruction bundle with a breakpoint, a breakpoint instruction can only ever generate a sigtrap (et.al.) (if executed) or sigsegv (if not accessible) so provided there is a breakpoint at the PC I don't think there is any possability of confusion (but again ignore decr pc after break :-).

So does this mean you're convinced that we can add SIGSEGV to the list
currently consisting of SIGILL and SIGEMT unconditionally?  I haven't
seen any ill effects on IA-32 and AMD64 (which are decr pc after
break).  I'll happilly check in the origional patch in mainline too.

We've found no evidence to the contrary - if something later breaks we can add that to the testsuite.


Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]