[Webkit-unassigned] [Bug 160414] New: [Tools] The GDB backtrace report tool don't checks GDB return code.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=160414

            Bug ID: 160414
           Summary: [Tools] The GDB backtrace report tool don't checks GDB
                    return code.
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: bugs-noreply at webkitgtk.org, lforschler at apple.com

There is an issue with current Debug builds of WebKitGTK+ and GDB. Check #159919

GDB=7.7.1 segfaults when trying to analyze a core produced on a Debug build of WebKitGTK+ without producing any output.

The WebKit tooling don't checks the return code and assumes that an empty stdout means that the corefile was not generated as expected.

So, it returns this:


"""
crash log for WebKitWebProcess (pid 7371):

Coredump core-pid_7371.dump not found. To enable crash logs:

- run this command as super-user: echo "|Tools/Scripts/process-linux-coredump /home/clopez/webkit/cores/core-pid_%p.dump" > /proc/sys/kernel/core_pattern
- enable core dumps: ulimit -c unlimited
- set the WEBKIT_CORE_DUMPS_DIRECTORY environment variable: export WEBKIT_CORE_DUMPS_DIRECTORY=/home/clopez/webkit/cores


STDERR: 
STDERR: warning: core file may not match specified executable file.
STDERR: <empty>
"""

Which is at best, misleading.

We should detect the return code from GDB and inform about it when it is non-zero.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160801/48d2c084/attachment.html>