Hi Eric,
> Also, I think many of the stackvma-*.c files have async-safety bugs, which
> render them less than perfect for use in stack overflow detection. For
> example, stackvma-procfs.c has a comment about why sigsegv_get_vma uses malloc
> () instead of alloca(), but in the case of a stack ov
Hi Eric,
> > When using both stackoverflow_install_handler and segv_handler_missing, a
> > SIGSEGV from dereferencing NULL will be wrongly treated as a stack
> > overflow on platforms that use mincore to check if the fault is near the
> > stack. In stackvma-mincore.c, mincore_is_near_this recogni
Eric Blake byu.net> writes:
> When using both stackoverflow_install_handler and segv_handler_missing, a
> SIGSEGV from dereferencing NULL will be wrongly treated as a stack
> overflow on platforms that use mincore to check if the fault is near the
> stack. In stackvma-mincore.c, mincore_is_near_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In porting c-stack to use libsigsegv, I discovered a bug in libsigsegv 2.5
on OpenBSD 4.0.
When using both stackoverflow_install_handler and segv_handler_missing, a
SIGSEGV from dereferencing NULL will be wrongly treated as a stack
overflow on platfo
