[Wayland-bugs] [Bug 60935] weston-launch does not handle weston signal exits

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Kristian Høgsberg <krh at bitplanet.net> ---
Oops, I was updating the bug too fast there.  That commit was never pushed and
Philip updated it to use different exit codes for weston signal exit vs
weston-launch signal exit.  This is now on weston master:

commit 7a3ec74cb61c0faae18dfec3782f58b91a193801
Author: Philipp Brüschweiler <blei42 at gmail.com>
Date:   Sun Mar 10 15:14:01 2013 +0100

    weston-launch: return better value if weston dies because of a signal

    Before this commit, weston-launch returned 0 if weston was killed by a
    signal. This makes it hard to automatically test weston by using
    weston-launch, as there is no way to know why weston was terminated.

    This commit makes weston-launch return 10+N instead, where N is the code
    of the signal that terminated weston. 10 was chosen because it allows a
    script to distinguish it from the case that weston-launch itself was
    killed by a signal (128+N), and does not overlap the standard exit codes
    defined in sysexits.h.

    Partial fix for https://bugs.freedesktop.org/show_bug.cgi?id=60935. I
    can't reproduce the SIGHUP using the fbdev backend.

    v3: better commit message.

-- 
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/20130319/f607af0c/attachment.html>