Bug 1059338

Summary: [abrt] emacs: terminate_due_to_signal(): emacs-24.3 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jason Grunhut <jgrunhut>
Component: emacsAssignee: Petr Hracek <phracek>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jchaloup, jonathan.underwood, phracek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d830ba49acfaa5a57b2f4f45633be00c26ec71bb
Whiteboard: abrt_hash:708fce4ef966d7b9988364e7ec22ad8ba8ead633
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-28 12:47:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jason Grunhut 2014-01-29 16:33:52 UTC 
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
Comment 1 Jason Grunhut 2014-01-29 16:34:00 UTC 
Created attachment 857143 [details]
File: backtrace
Comment 2 Jason Grunhut 2014-01-29 16:34:02 UTC 
Created attachment 857144 [details]
File: cgroup
Comment 3 Jason Grunhut 2014-01-29 16:34:05 UTC 
Created attachment 857145 [details]
File: core_backtrace
Comment 4 Jason Grunhut 2014-01-29 16:34:07 UTC 
Created attachment 857146 [details]
File: dso_list
Comment 5 Jason Grunhut 2014-01-29 16:34:09 UTC 
Created attachment 857147 [details]
File: environ
Comment 6 Jason Grunhut 2014-01-29 16:34:11 UTC 
Created attachment 857148 [details]
File: limits
Comment 7 Jason Grunhut 2014-01-29 16:34:13 UTC 
Created attachment 857149 [details]
File: maps
Comment 8 Jason Grunhut 2014-01-29 16:34:17 UTC 
Created attachment 857150 [details]
File: open_fds
Comment 9 Jason Grunhut 2014-01-29 16:34:19 UTC 
Created attachment 857151 [details]
File: proc_pid_status
Comment 10 Jason Grunhut 2014-01-29 16:34:21 UTC 
Created attachment 857152 [details]
File: var_log_messages
Comment 11 Jan Chaloupka 2014-07-28 12:37:39 UTC 
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
Comment 12 Jason Grunhut 2014-07-28 12:40:24 UTC 
Hi Jan,

I don't think this problem is reproducible. If it is, it is not easily so.

Sorry,
Jason
Comment 13 Jan Chaloupka 2014-07-28 12:47:12 UTC 
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
Comment 14 Jan Chaloupka 2014-07-29 11:37:05 UTC 
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