Ticket #3140 (closed bug: invalid)

Opened 16 months ago

Last modified 16 months ago

SIGSEGV handler not called upon stack overflow

Reported by: bhaible Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Platform: All
Blocking:

Description

After installing a SIGSEGV handler and an alternate stack (and verifying that both the sigaction and sigaltstack system calls succeeded!), a stack overflow still does not invoke the SIGSEGV handler.

Expected behaviour of the attach program: A message on stderr, either "program error" or "stack overflow".

Actual behaviour: A dialog allowing to debug the program. If I enter Debug, then "continue", the error message on stderr is "Segmentation violation" - the handler was still not caught.

This works on BeOS.

Attachments

stack-overflow-bug.c Download (1.8 KB) - added by bhaible 16 months ago.
test program provoking a stack overflow
haiku-long-double-bug.png Download (8.3 KB) - added by bhaible 16 months ago.
screenshot of dialog appearing

Change History

Changed 16 months ago by bhaible

test program provoking a stack overflow

Changed 16 months ago by bhaible

screenshot of dialog appearing

Changed 16 months ago by bhaible

Oops, my mistake. When I add SA_ONSTACK to the sigaction flags, the signal handler is called.

You can close or trash this ticket.

Changed 16 months ago by anevilyak

  • status changed from new to closed
  • resolution set to invalid

Thanks for the note!

Note: See TracTickets for help on using tickets.