[Wayland-bugs] [Bug 63004] weston-launch always crashes with SIGHUP

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 22 10:45:27 PDT 2013


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

--- Comment #5 from Joe Konno <joe.konno at linux.intel.com> ---
Each of the signals I send to the weston process are reported as "caught" in
weston-launch stdout, last stdout message is "Hangup", unless otherwise noted.

Here's what I get when killing the weston process with various signals:

  * kill -s SIGHUP <weston pid>: weston-launch $? = 129
  * kill -s SIGINT <weston pid>: weston-launch $? = 0
  * kill -s SIGQUIT <weston pid>: weston-launch $? = 0
  * kill -s SIGILL <weston pid>: weston-launch $? = 129
    - no stdout indicating catch, framebuffer hangs, weston-launch needs to be
re-executed to bring back
  * kill -s SIGABRT <weston pid>: weston-launch $? = 129
  * kill -s SIGFPE <weston pid>: weston-launch $? = 129
    - no stdout indicating catch, framebuffer hangs, weston-launch needs to be
re-executed to bring back
  * kill -s SIGSEGV <weston pid>: weston-launch $? = 129
  * kill -s SIGTERM <weston pid>: weston-launch $? = 129

-- 
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/20130722/a43950bc/attachment-0001.html>


More information about the Wayland-bugs mailing list