Closed GoogleCodeExporter closed 9 years ago
See here for when you get SIGBUS:
http://lkml.iu.edu/hypermail/linux/kernel/1008.1/02299.html
The test case arranges for some memory to be mapped before the stack segment so
that when the stack segment grows down a bit "we'll get a nice SIGBUS just as
the stack touches the page just above the mapping".
Original comment by jay.f...@gmail.com
on 9 Jan 2015 at 4:29
Right. We already handle SIGBUS on Mac, I think we should just do this on Linux
as well.
Original comment by samso...@google.com
on 9 Jan 2015 at 10:49
Original comment by samso...@google.com
on 9 Jan 2015 at 10:49
Could you check if adding SIGBUS to IsDeadlySignal() in sanitizer_linux.cc will
fix the problem for you?
Original comment by samso...@google.com
on 9 Jan 2015 at 11:09
Yes, that's exactly what I did to fix it locally!
- return (signum == SIGSEGV) && common_flags()->handle_segv;
+ return (signum == SIGSEGV || signum == SIGBUS) &&
common_flags()->handle_segv;
This is what we already do in sanitizer_darwin.cc anyway.
Original comment by jay.f...@gmail.com
on 10 Jan 2015 at 8:25
Can you prepare a patch (with test case)?
Original comment by samso...@google.com
on 12 Jan 2015 at 3:00
Looks like r225630 takes care of this.
Original comment by samso...@google.com
on 12 Jan 2015 at 7:26
Original issue reported on code.google.com by
jay.f...@gmail.com
on 9 Jan 2015 at 4:26