<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - SIGABRT and SIGSEGV in epoll_wait during wl_event_loop_dispatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77457#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - SIGABRT and SIGSEGV in epoll_wait during wl_event_loop_dispatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77457">bug 77457</a>
from <span class="vcard"><a class="email" href="mailto:ullysses.a.eoff@intel.com" title="U. Artie Eoff <ullysses.a.eoff@intel.com>"> <span class="fn">U. Artie Eoff</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=77457#c5">comment #5</a>)
<span class="quote">> I just remembered that weston does have handlers for these two signals. They
> both execute on_caught_signal(), around
> <a href="http://cgit.freedesktop.org/wayland/weston/tree/src/compositor.c#n3885">http://cgit.freedesktop.org/wayland/weston/tree/src/compositor.c#n3885</a> which
> then raises SIGTRAP.
>
> This might affect the process exit code, but surely it won't exit with
> status 0, right? But the exit code might not reflect ABRT or SEGV properly.
> Not sure if that could be a problem.</span >
Right. As long as weston exits with any non-zero status for these signals, then
it shouldn't be a problem in most cases. Basically, when doing test automation
we want to be sure that a weston crash is detectable with a non-zero exit code
so that the test result can reflect that correctly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>