[Bug 127] On segfault, with "signals on exceptions" enabled SableVM hangs

http://sablevm.org/bugs/show_bug.cgi?id=127





------- Additional Comments From [email protected]  2005-04-08 02:34 -------
[FYI, I am unable to reproduce an Eclipse segfault...  Maybe you should specify
more precisely how to reproduce this, and which version of Eclipse to run.]

About the suggestion: there are 2 ways:
1- if the signal handler detects that the thread is not running Java, it lets
the raised segfault crash the program (core dump).  Neat idea, but how do you do
that?
2- alternatively, we could register and unregister for catching segfaults in
_svmm_resuming_java() and _svmm_stopping_java(). This would probably have a
major performance impact (negative).

Or, why don't you simply turn debugging on (e.g. do not -DNDEBUG)?  This was
SableVM does set a global variable to true when a segfault *is* expected, and is
thus able to detect "real" segfaults.  This should be sufficient for identifying
buggy native code.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.