Exception trace for i386, mark II
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Andi Kleen
This is a new implementation of exception trace for i386.
It adds a new exception-trace sysctl (default to off), which when enabled triggers printk for unhandled fault signals (SIGSEGV etc.).
Isn't this very similar to the KERN_S390_USER_DEBUG_LOGGING sysctl? Maybe the code can be merged, or at least they can use the same numeric value for the sysctl.
Arnd <><
Quoted 11 lines · Arnd Bergmann
Quoted 5 lines · Andi Kleen
This is a new implementation of exception trace for i386.
It adds a new exception-trace sysctl (default to off), which when enabled triggers printk for unhandled fault signals (SIGSEGV etc.).
Isn't this very similar to the
KERN_S390_USER_DEBUG_LOGGINGsysctl? Maybe the code can be merged, or at least they can use the same numeric value for the sysctl.
No problem from my side, although it seems a bit pointless for just an sysctl. I don't think anybody expects new sysctls binary values to be stable anymore - all the distribution kernels vary them widely.
-Andi