[DragonFlyBSD - Bug #1442] blocking SIGSEGV and triggering a segment violation produces an all CPU consuming process

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #1442 has been updated by tuxillo.

Description updated
Category set to Other
Assignee changed from 0 to tuxillo
Target version set to 3.8.0

Grab.

----------------------------------------
Bug #1442: blocking SIGSEGV and triggering a segment violation produces an all CPU consuming process
http://bugs.dragonflybsd.org/issues/1442#change-11808

* Author: corecode
* Status: New
* Priority: Normal
* Assignee: tuxillo
* Category: Other
* Target version: 3.8.0
----------------------------------------
If a process blocks (or ignores?) SIGSEGV (or SIGFPE, SIGILL, SIGBUS, etc.) and
then triggers the associated signal without having a handler installed, the
process/thread will be stuck on the triggering instruction without any hope.

I think the kernel should detect such a situation (i.e. trap leading to
blocked/ignored signal without handler) and should kill the process.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account