GNOME Bugzilla – Bug 696328
empathy-debugger crashed with SIGSEGV
Last modified: 2013-09-09 13:24:14 UTC
Originally reported at: https://bugs.launchpad.net/bugs/1123068 Just opening help -> debug caused this error after a second or two. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: empathy 3.6.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 12 14:35:16 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/empathy-debugger InstallationDate: Installed on 2012-11-09 (94 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121109) MarkForUpload: True ProcCmdline: /usr/bin/empathy-debugger -s Empathy.Call ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=<set> PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f42338d58a6: mov 0x1c(%rax),%esi PC (0x7f42338d58a6) ok source "0x1c(%rax)" (0x0000001c) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: empathy-debugger crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (gnome-settings-daemon:2194): media-keys-plugin-WARNING **: Unable to get default sink (gnome-settings-daemon:2194): media-keys-plugin-WARNING **: Unable to get default sink (gnome-settings-daemon:2194): media-keys-plugin-WARNING **: Unable to get default sink
+ Trace 231670
I can reproduce this but valgrind isn't helping :(
Seems related to https://bugs.freedesktop.org/show_bug.cgi?id=63196 I tried with Cairo master and now get this fatal error: (lt-empathy-debugger:25388): Gdk-ERROR **: The program 'lt-empathy-debugger' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2809 error_code 11 request_code 130 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Actually this seems to be a Gtk+ issue. I doesn't crash with Gtk+ 3.6.4 but does with 3.8 (just tested with f9dd457b25c66bf86925369339766ceb9112a92c here).
Interesting, if I comment out "g_object_set (G_OBJECT (cell), "text", tp_debug_message_get_message (msg), NULL);" in debug_window_message_formatter() it doesn't crash.
Created attachment 254478 [details] [review] debug-window: ellipsize the message text renderer Ridiculously long messages were crashing empathy-debugger because Pango weren't able to display them all.
Review of attachment 254478 [details] [review]: Yay!
Attachment 254478 [details] pushed as fa72bed - debug-window: ellipsize the message text renderer