You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CPython faulthandler module installs fault handlers for the SIGSEGV, SIGFPE, SIGABRT, SIGBUS, and SIGILL signals. Unfortunately, our experience shows that this level of OS/process manipulation destabilizes the Java process that is running Ghidra + Ghidrathon, often resulting in a crash (SIGSEGV). For the time being, we need to document that Ghidrathon does not support the faulthandler module (and likely never will). Python modules that use the faulthandler module, e.g. pytest, should be configured to disable it, if possible. If the faulthandler module cannot be disabled then Ghidrathon does not support the Python module(s) that use it. We should also note that, in general, Ghidrathon's behavior for this level of OS/process manipulation is undefined, at best.
The CPython
faulthandler
module installs fault handlers for theSIGSEGV
,SIGFPE
,SIGABRT
,SIGBUS
, andSIGILL
signals. Unfortunately, our experience shows that this level of OS/process manipulation destabilizes the Java process that is running Ghidra + Ghidrathon, often resulting in a crash (SIGSEGV
). For the time being, we need to document that Ghidrathon does not support thefaulthandler
module (and likely never will). Python modules that use thefaulthandler
module, e.g.pytest
, should be configured to disable it, if possible. If thefaulthandler
module cannot be disabled then Ghidrathon does not support the Python module(s) that use it. We should also note that, in general, Ghidrathon's behavior for this level of OS/process manipulation is undefined, at best.Known Python module using
faulthandler
:pytest
-p no:faulthandler
at invocation; see hereThe text was updated successfully, but these errors were encountered: