[Wayland-bugs] [Bug 65910] New: [bug] Killing weston-launch causes segv in desktop-shell

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 65910
          Assignee: wayland-bugs at lists.freedesktop.org
           Summary: [bug] Killing weston-launch causes segv in
                    desktop-shell
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: joe.konno at linux.intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: weston
           Product: Wayland

When weston-launch is killed with SIGINT or SIGTERM, weston-launch exits as
expected. However, attaching to the desktop-shell process prior to killing
weston-launch reveals that desktop-shell segfaults (100% of the time).

Further, the segv is masked. Running `echo $?` immediately after killing
weston-launch does not give any indication of the desktop-shell segv. There is
no stdout or stderr log messages indicating that an error occurred. This is
undesired behavior.

Steps to reproduce:

  1. Run as a normal user (member of weston-launch group):
    weston-launch

  2. Attach gdb to the desktop-shell process, continue execution

  3. Kill weston-launch, either with SIGTERM or SIGINT

  4. gdb will catch a segv

It is expected that weston-launch somehow communicate an unclean exit from its
shell (or modules).

In actuality, whatever launched weston-launch is not informed of the unclean
exit.

State of (select components of) the s/w stack:
wayland (master) heads/master-0-g7094441
mesa (HEAD) mesa-9.1.3-0-gf32ec82
cairo (HEAD) 1.12.8-0-gcc16291
weston (master) heads/master-0-ga58290b

-- 
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/20130618/8f4ee988/attachment.html>