Description of problem: M-x helm-ag-r -- then entering a couple letters -- some result flickers and then Emacs is dead, helm-ag-r was changed to have its first line -- the one immediately after (interactive) to be (setq helm-ag-r-dir-or-file (or file-or-directory (ag/project-root default-directory))) .. Version-Release number of selected component: emacs-24.3-13.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: emacs crash_function: terminate_due_to_signal executable: /usr/bin/emacs-24.3 kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 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 multibyte_chars_in_text at /usr/src/debug/emacs-24.3/src/character.c:539 #4 make_specified_string at /usr/src/debug/emacs-24.3/src/alloc.c:2141 #5 Ffile_name_as_directory at /usr/src/debug/emacs-24.3/src/fileio.c:544 #6 Ffuncall at /usr/src/debug/emacs-24.3/src/eval.c:2778 #7 exec_byte_code at /usr/src/debug/emacs-24.3/src/bytecode.c:900 #8 funcall_lambda at /usr/src/debug/emacs-24.3/src/eval.c:3010 #9 Ffuncall at /usr/src/debug/emacs-24.3/src/eval.c:2839 #10 exec_byte_code at /usr/src/debug/emacs-24.3/src/bytecode.c:900
Created attachment 863011 [details] File: backtrace
Created attachment 863012 [details] File: cgroup
Created attachment 863013 [details] File: core_backtrace
Created attachment 863014 [details] File: dso_list
Created attachment 863015 [details] File: environ
Created attachment 863016 [details] File: limits
Created attachment 863017 [details] File: maps
Created attachment 863018 [details] File: open_fds
Created attachment 863019 [details] File: proc_pid_status
Created attachment 863020 [details] File: var_log_messages
Hi, Samium, this bug looks interesting to me. Can you reproduce this issue anytime? If so, please install the following rpm $ cd /tmp $ wget https://jchaloup.fedorapeople.org/emacs-24.3-18.fc20.x86_64.rpm # rpm -Uvh emacs-24.3-18.fc20.x86_64.rpm Then reproduce the issue and upload generated core. After reproducing, just run # yum distro-sync emacs Thank you Jan
Update 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
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