Version-Release number of selected component: emacs-24.3-13.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: emacs plot_dyn.pro crash_function: terminate_due_to_signal executable: /usr/bin/emacs-24.3 kernel: 3.12.7-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 terminate_due_to_signal at /usr/src/debug/emacs-24.3/src/emacs.c:344 #2 emacs_abort at /usr/src/debug/emacs-24.3/src/sysdep.c:2152 #3 check_glyph_memory at /usr/src/debug/emacs-24.3/src/dispnew.c:2344 #4 shut_down_emacs at /usr/src/debug/emacs-24.3/src/emacs.c:1922 #5 Fkill_emacs at /usr/src/debug/emacs-24.3/src/emacs.c:1835 #6 terminate_due_to_signal at /usr/src/debug/emacs-24.3/src/emacs.c:326 #7 handle_fatal_signal at /usr/src/debug/emacs-24.3/src/sysdep.c:1638 #8 deliver_process_signal at /usr/src/debug/emacs-24.3/src/sysdep.c:1580 #10 poll at ../sysdeps/unix/syscall-template.S:81 #12 _xcb_conn_wait at xcb_conn.c:414
Created attachment 857143 [details] File: backtrace
Created attachment 857144 [details] File: cgroup
Created attachment 857145 [details] File: core_backtrace
Created attachment 857146 [details] File: dso_list
Created attachment 857147 [details] File: environ
Created attachment 857148 [details] File: limits
Created attachment 857149 [details] File: maps
Created attachment 857150 [details] File: open_fds
Created attachment 857151 [details] File: proc_pid_status
Created attachment 857152 [details] File: var_log_messages
Hi, Jason, is this issue reproducible? Can you list steps how to reproduce it? With plot_dyn.pro file and other emacs files? List of emacs extensions would be great. Without a proper reproduces I am unable to find out what went wrong. Thanks Cheers Jan
Hi Jan, I don't think this problem is reproducible. If it is, it is not easily so. Sorry, Jason
From core_backtrace, I see only *xcb_* functions calls. Backtrace is on the other hand almost informationless. If the crash occurs again, don't hesitate to reopen this bug. New backtrace could give more information about what is going on. Thank you for your time Jan
Steps to create core with full backtrace information for emacs: $ cd /tmp download the latest emacs build from https://jchaloup.fedorapeople.org for your distribution and architecture (wget can be used). Should be always actual release in fedora + 1. $ wget https://jchaloup.fedorapeople.org/emacs-24.3-19.fc20.x86_64.rpm install downloaded rpm, release can vary # rpm -Uvh emacs-24.3-19.fc20.x86_64.rpm Then reproduce the issue and upload generated core. After reproducing, just run # yum distro-sync emacs