Description of problem: Opened a Python file for editing from the command line. This appeared on the console: Backtrace: emacs[0x4f98e3] emacs[0x4def01] emacs[0x4f837e] emacs[0x4f8503] /lib64/libpthread.so.0(+0xf720)[0x7fe84d45c720] /lib64/libc.so.6(getenv+0xad)[0x7fe84d0c777d] /lib64/libc.so.6(+0x302e1)[0x7fe84d0bf2e1] /lib64/libgtk-3.so.0(+0x18996a)[0x7fe85262c96a] /lib64/libgobject-2.0.so.0(g_type_class_ref+0x4ae)[0x7fe850e9ad3e] /lib64/libgobject-2.0.so.0(g_object_newv+0x279)[0x7fe850e834a9] /lib64/libgobject-2.0.so.0(g_object_new+0x104)[0x7fe850e83c24] /lib64/libgtk-3.so.0(+0x29bfef)[0x7fe85273efef] /lib64/libgobject-2.0.so.0(g_type_create_instance+0x1fb)[0x7fe850e9d68b] /lib64/libgobject-2.0.so.0(+0x155b5)[0x7fe850e815b5] /lib64/libgobject-2.0.so.0(g_object_newv+0x22d)[0x7fe850e8345d] /lib64/libgobject-2.0.so.0(g_object_new+0x104)[0x7fe850e83c24] /lib64/libgtk-3.so.0(+0x29e031)[0x7fe852741031] /lib64/libgtk-3.so.0(gtk_main_do_event+0x258)[0x7fe85264e048] /lib64/libgdk-3.so.0(+0x4efc2)[0x7fe85223dfc2] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x166)[0x7fe850b892a6] /lib64/libglib-2.0.so.0(+0x49628)[0x7fe850b89628] /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fe850b896dc] /lib64/libgtk-3.so.0(gtk_main_iteration+0x15)[0x7fe85264d7d5] emacs[0x4b34e2] emacs[0x4e6331] emacs[0x4e5c85] emacs[0x598872] emacs[0x552e7f] emacs[0x55401c] emacs[0x552e7f] emacs[0x5882cb] emacs[0x55297f] emacs[0x552c8b] emacs[0x55401c] emacs[0x552e7f] emacs[0x5882cb] emacs[0x552c8b] emacs[0x55401c] emacs[0x552e7f] emacs[0x5882cb] emacs[0x552c8b] Version-Release number of selected component: emacs-24.3-24.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 crash_function: terminate_due_to_signal executable: /usr/bin/emacs-24.3 kernel: 3.15.10-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 terminate_due_to_signal #2 handle_fatal_signal #3 deliver_fatal_thread_signal #5 getenv at /lib64/libc.so.6 #6 __dcigettext at /lib64/libc.so.6 #7 gtk_image_class_intern_init at /lib64/libgtk-3.so.0 #8 g_type_class_ref at /lib64/libgobject-2.0.so.0 #11 gtk_tooltip_init at /lib64/libgtk-3.so.0 #12 g_type_create_instance at /lib64/libgobject-2.0.so.0 #13 g_object_new_internal at /lib64/libgobject-2.0.so.0
Created attachment 939054 [details] File: backtrace
Created attachment 939055 [details] File: cgroup
Created attachment 939056 [details] File: core_backtrace
Created attachment 939057 [details] File: dso_list
Created attachment 939058 [details] File: environ
Created attachment 939059 [details] File: limits
Created attachment 939060 [details] File: maps
Created attachment 939061 [details] File: open_fds
Created attachment 939062 [details] File: proc_pid_status
Created attachment 939063 [details] File: var_log_messages
Hello Christopher, thank you for your report. Does the problem occurs every time or has it happened just once? If it is not reproducible, it is a glitch that occurs from time to time. Hard to trace any origin of the cause. Unfortunately, the backtrace is missing a lot of information. Thanks Jan
It only happened once. Is there anything I can do to get a more complete backtrace? I'm doing "debuginfo-install emacs" though I would have expected abrt to do the equivalent when analyzing the crash dump.
debuginfo-install is definitely better. Even better have not opmized build of emacs with it. And the best to have a reproducer too. But catch the right crash is like a magic :) Maybe this time we will get better information :). Thanks anyway.
I'm using the stock Fedora build; not sure whether it's optimized.
Hi reporter, I am closing this bug as backtrace does not contain complete information about this issue. This bug comes under those bugs that are hard to reproduce, backtrace does not contain all necessary data due to optimization or are caused by a known glitch in emacs. If you manage to reproduce this issue more than once don't hesitate to reopen this bug. Kind regards Jan