<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#c7">Comment # 7</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: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=165656#c4">comment #4</a>)
<span class="quote">> The backtraces you attached don't have any local variables or line numbers.
> Can you do a build with debug info (-DCMAKE_BUILD_TYPE=RelWithDebInfo) and
> post another backtrace taken with 'bt full'? They're also missing debuginfo
> from libX11.so which needs to be fixed. I would always insist on this
> quality level to have a more useful crash report.</span >
The backtraces have line numbers, why you say that?
They are much more readable if you demangle the symbols. Example:
curl -s '<a href="https://bug-165656-attachments.webkit.org/attachment.cgi?id=297082">https://bug-165656-attachments.webkit.org/attachment.cgi?id=297082</a>' | c++filt
What I see in this backtrace is that the crash happens because some X error not trapped is emitted. This probably means that the fix on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] BadDamage X Window System error in WebKit::AcceleratedBackingStoreX11::update when called from WebPageProxy::exitAcceleratedCompositingMode"
href="show_bug.cgi?id=164303">bug 164303</a> is incompleted and more X error than BadDrawable and BadDamage should be trapped.
It will be useful to know which X error caused this.
Did you got printed on the terminal some information about the X error that caused webkit to abort?</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>