[Webkit-unassigned] [Bug 162497] [GTK] [2.14.0] _cairo_surface_has_snapshots (surface)' failed

[bugzilla-daemon at webkit.org]

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

--- Comment #12 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to comment #11)
> The full read out is at the start of the bug report.
> 
> How do you show the local variables?

'bt full' just like you showed there... in the first comment you have a backtrace without any line numbers or local variables, in this last comment you have a partial backtrace with local variables 

Maybe it would be better to show you what we expect. Something like this:

https://bugzilla.redhat.com/attachment.cgi?id=1219931

We don't usually need all threads, just one is usually enough, and we don't need all the library state at the bottom, just the output of 'bt full'. But that needs to be a complete stacktrace of the crashing thread from the top frame down to the bottom one. You need this every time you report a C/C++ crash to the developers of any application; there's nothing WebKit-specific about this. Most distros make this easy; in Fedora gdb tells you run a 'dnf debuginfo-install' command, you wait two minutes for the debuginfo to be installed, and then you get the stacktrace again. If you're building everything yourself in /usr/local with no debuginfo then consequently you've got to rebuild everything in the stack with -g to get the debuginfo.

-- 
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/20161202/e084195f/attachment.html>