* segv and function descriptors
@ 2004-04-05 19:13 Andrew Cagney
0 siblings, 0 replies; only message in thread
From: Andrew Cagney @ 2004-04-05 19:13 UTC (permalink / raw)
To: gdb
Hello,
I'm trying to come up with a robust test for GDB backtracing through a
NULL function pointer vis:
segv_handler
<signal trampoline>
0
main
ABIs using function descriptors unfortunatly end up with the stack:
segv_handler
<signal trampoline>
main
This is because the call ((*)())0 turns into a data (the descriptor)
access at 0 rather than a code access.
Can anyone think of a way to detect a descriptor abi? If I know that, I
can fudge a null descriptor and hence always cause the correct segv.
Andrew
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-04-05 19:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-05 19:13 segv and function descriptors Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).