<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c9">Comment # 9</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 <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to <a href="show_bug.cgi?id=77457#c7">comment #7</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>