<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] UIProcess from WebKitGtk+ 2.15.2 SIGSEGVs in WebKit::AcceleratedBackingStoreX11::update(WebKit::LayerTreeContext const&) () at Source/WebKit2/UIProcess/gtk/AcceleratedBackingStoreX11.cpp:145"
href="https://bugs.webkit.org/show_bug.cgi?id=165656#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] UIProcess from WebKitGtk+ 2.15.2 SIGSEGVs in WebKit::AcceleratedBackingStoreX11::update(WebKit::LayerTreeContext const&) () at Source/WebKit2/UIProcess/gtk/AcceleratedBackingStoreX11.cpp:145"
href="https://bugs.webkit.org/show_bug.cgi?id=165656">bug 165656</a>
from <span class="vcard"><a class="email" href="mailto:agomez@igalia.com" title="Andres Gomez Garcia <agomez@igalia.com>"> <span class="fn">Andres Gomez Garcia</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=165656#c9">comment #9</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=165656#c5">comment #5</a>)
> > I'm sorry Michael, but I disagree.
> >
> > This is not a reasonable request.
>
> It's not? If you try to report a crash report with an incomplete backtrace
> it should be closed as incomplete/invalid. Why should we waste time with
> this when (almost) everyone else is reporting bugs with good quality
> backtraces...? In this case we need to see the local variables in
> XErrorTrapper::errorEvent to figure out what the XError was, your backtrace
> doesn't have them, the backtraces we've come to expect would.</span >
I've explained the steps to reproduce.
<span class="quote">> If you were a Fedora or openSUSE user, I would say to run the
> debuginfo-install command given to you by gdb and then take the backtrace
> again. It takes all of two minutes and is not unreasonable at all. Since
> you're using Debian, you've got to do it manually and I know that takes
> longer, but that's a distro problem and doesn't mean it's optional. In fact,</span >
The distro is completely irrelevant since I'm using jhbuild. Please, read the descriptions of the reported bugs.
<span class="quote">> since you built WebKit yourself, you'd already have the debuginfo for the
> frames we need had you used -g instead of -g1. So using -g is the minimal
> change I would make next time you build WebKit. (I also think it's a really</span >
-g1 is the difference between having an usable and debuggable ephy or not having it at all. These flags are not there by mistake but, actually by advice from you, developers.
<span class="quote">> bad idea to use G_DISABLE_CAST_CHECKS. That's going to make lots of bugs
> much harder to solve, but that's not likely an issue here.)</span >
Same than above.</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>