<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve GDB backtrace generation for GTK/EFL"
href="https://bugs.webkit.org/show_bug.cgi?id=128928#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve GDB backtrace generation for GTK/EFL"
href="https://bugs.webkit.org/show_bug.cgi?id=128928">bug 128928</a>
from <span class="vcard"><a class="email" href="mailto:clopez@igalia.com" title="Carlos Alberto Lopez Perez <clopez@igalia.com>"> <span class="fn">Carlos Alberto Lopez Perez</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=128928#c4">comment #4</a>)
<span class="quote">> Nice investigation indeed.
>
> The right thing to do is to get cores from coredumpctl so we don't have to
> mess around with changing the core_pattern. I'd be interested in working on
> this eventually (for some large value of eventually).</span >
I guess that would require the users to run systemd. This can be problematic on the bots (they run on unprivileged containers, and systemd don't plays nice there)
Also I'm not sure if it will solve the main problem, that is:
* Due to WebKit multiprocess model, our tooling for the tests can only know the pid of WebKitTestRunner, but not the pid of any of the childs (WebKitWebProcess, WebKitNetworkProcess, etc).
So, when you get a coredump for WebKitWebProcess (for example) with pid NNNN you can't tell which test caused the crash.
The only reasonable way of solving this that I see is setting an environment variable (that the childs will inherit) with the test name.
When it crashes, the program invoked via the pipe in core_pattern will have access to /proc/$pid/environ and can read this.
With coredumpctl, such program will be systemd-coredump.
So... the main question.... is coredumpctl able to get and print the environ variables that a program had defined when it crashed for a given coredump? If is not, I don't think it will be of any help here.</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>