Comment #3 on issue 302 by [email protected]: Add ability to
forward SEGVs to ASAN handler
http://code.google.com/p/address-sanitizer/issues/detail?id=302
Well, both of you are right. That said, calling
__sanitizer_print_stack_trace() does not feel very "future-proof"... ASan
SEGV handler may get richer features in the future.
And allow_user_segv_handler fix my "workaround" case (well, make it
asan-hacking free at least). However, I still would like something
more "packaged". Having some built-in chaining facility in asan would help
making the code both simpler and safer.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
