<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - [bug] Killing weston-launch causes segv in desktop-shell"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=65910">65910</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[bug] Killing weston-launch causes segv in desktop-shell
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>joe.konno@linux.intel.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>weston
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Wayland
          </td>
        </tr></table>
      <p>
        <div>
        <pre>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</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>