<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Not possible to GDB WebKitGtk+ 2.13.3: demangler-warning: unable to demangle"
href="https://bugs.webkit.org/show_bug.cgi?id=159919#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Not possible to GDB WebKitGtk+ 2.13.3: demangler-warning: unable to demangle"
href="https://bugs.webkit.org/show_bug.cgi?id=159919">bug 159919</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=159919#c7">comment #7</a>)
<span class="quote">> The bug is definitive this one:
> <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159</a> and is still present in
> last GDB git master.
>
> I tried using lldb (LLVM debugger) and its also crashing (segfaults)...
>
>
> So... at least on my environment I'm complete unable to use a debugger on
> current trunk of WebKit with Debug builds.
>
>
> Is anybody here able to work with gdb/llvdb and debug builds?</span >
BTW, adrian perez pointed me to this very helpful trick:
* Put in your ~/.gdbinit file:
set demangle-style none
* Then pipe the output of GDB through c++filt (a stand-alone demangler).
It works for me.
I see that the WebKit tooling for generating GDB crash logs is already piping the output through c++filt. So I'm going to just set this line on the GTK+ bots ~/.gdbinit files.</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>