memory fault error reporting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Low
|
Unassigned |
Bug Description
On those architectures where :C-STACK-
*FEATURES*, we handle SIG_MEMORY_FAULT (SEGV or BUS) on an altstack,
so we cannot handle the signal directly (as in interrupt_
in the case when the signal comes from some external agent (the user
using kill(1), or a fault in some foreign code, for instance).
Tthis is fixed by calling arrange_
function, but as a result the error reporting is brittle: the fault address is passed to
lisp code in a global variable, which is decidedly not threadsafe.
lt occurred. We should arrange such that arguments can be passed to the function
called from arrange_
without suffering from memory leaks.
There are probably other use-cases of passing arguments via a_r_t_l_f as well.
description: | updated |
description: | updated |
Changed in sbcl: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
Fixed in 60b6cdb8074978c abecd2972105ebc 851da41bf5.