[Wayland-bugs] [Bug 77457] SIGABRT and SIGSEGV in epoll_wait during wl_event_loop_dispatch

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=77457

--- Comment #9 from Pekka Paalanen <ppaalanen at gmail.com> ---
(In reply to comment #7)
> I mean....
> 
> SIGSEGV, SIGABRT and SIGKILL signals are exiting with 'non zero' exit code.
> But when weston receives SIGABRT and SIGSEGV signals, I see below message on
> tty.
> 
> Trace/breakpoint trap (core dumped) – (weston)_main

Yes, that is the current intended behaviour. If you read the comment in
on_caught_signal(), you'll see why it's there.

If we were to re-raise the SEGV or ABRT, using gdb might be harder. OTOH, we
could have a command line switch for choosing gdb-friendly operation.

But, like Artie said, until someone sees a practical problem here, things
should be ok as is.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20140416/7f22b1a0/attachment.html>