Bug #1442

blocking SIGSEGV and triggering a segment violation produces an all CPU consuming process

Added by corecode about 7 years ago. Updated over 2 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:tuxillo% Done:


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.


#1 Updated by tuxillo over 2 years ago

  • Description updated (diff)
  • Category set to Other
  • Assignee changed from 0 to tuxillo
  • Target version set to 3.8.0


Also available in: Atom PDF