Bug 1104012
Summary: | crashes on startup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ales Kozumplik <akozumpl> |
Component: | emacs | Assignee: | Jan Chaloupka <jchaloup> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | jchaloup, jonathan.underwood, jzeleny, phracek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | emacs-24.3-22.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-15 02:52:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ales Kozumplik
2014-06-03 05:48:40 UTC
There it is: http://akozumpl.fedorapeople.org/core.3657 Hi, Ales could you attach .emacs.desktop as well? Have you been able to reproduces this crash again? Thanks Jan Hello, yes I have but then I removed the .desktop file and started the workspace over. Does it still occur after removing .desktop file? If so, can you describe me the steps that take to a succesfull crash? What was open, in what order, any information is a plus. Thank you Jan, no, it does not happen with the new .desktop file. I hoped that the core file would lead to the right path to debugging this. I'll attach any further information once I manage to reproduce this again. #0 0x000000000055f0e0 in hash_lookup () #1 0x000000000048fe30 in code_convert_string () #2 0x00000000005109ed in Fexpand_file_name () #3 0x00000000005103bf in Fexpand_file_name () #4 0x0000000000515f9c in Fdo_auto_save () #5 0x00000000004deca4 in shut_down_emacs () #6 0x00000000004deeca in terminate_due_to_signal () #7 0x00000000004f833e in handle_fatal_signal () #8 0x00000000004f84c3 in deliver_fatal_thread_signal () #9 <signal handler called> #10 0x000000000053a880 in mark_object () #11 0x00000000004f0ccc in mark_kboards () #12 0x000000000053b275 in Fgarbage_collect () #13 0x0000000000552bce in Ffuncall () #14 0x00000000005882bb in exec_byte_code () #15 0x00000000005529bf in funcall_lambda () ...repeating stuff... #68 0x0000000000552ccb in Ffuncall () #69 0x00000000005882bb in exec_byte_code () #70 0x0000000000551ddd in apply_lambda () #71 0x00000000005521a2 in eval_sub () #72 0x000000000055574d in Feval () #73 0x00000000005512ca in internal_condition_case () #74 0x00000000004df3d6 in top_level_1 () #75 0x0000000000551171 in internal_catch () #76 0x00000000004e3b1f in recursive_edit_1 () #77 0x00000000004e3e34 in Frecursive_edit () #78 0x0000000000417125 in main () This is the backtrace from your core. In most cases it does not contain enough informations. First in order to be able to reproduce the crash a need to know all args of program, all files that has been read, what has been pressed/done in the program, etc. Otherwise it is impossible to find out what when wrong :). Thank you for your help. Please run this command and send me its output: $ rpm -qa | grep emacs Content of your ~/.emacs file contains additional information so if they are not confidential, please attached it as well. Good luck with hunting this bug :) emacs-24.3-16.fc20.x86_64 emacs-common-w3m-1.4.435-0.5.20110225cvs.fc20.noarch emacs-color-theme-6.6.0-8.fc20.noarch emacs-apel-10.8-6.fc20.noarch emacs-w3m-1.4.435-0.5.20110225cvs.fc20.noarch xemacs-filesystem-21.5.34-5.fc20.noarch emacs-w3m-el-1.4.435-0.5.20110225cvs.fc20.noarch emacs-git-1.9.0-1.fc20.noarch emacs-filesystem-24.3-13.fc20.noarch emacs-common-24.3-16.fc20.x86_64 emacs-nox-24.3-16.fc20.x86_64 emacs-el-24.3-13.fc20.noarch BTW, it should be possible to get more detailed backtrace using debuginfo packages. Just happened again today: http://akozumpl.fedorapeople.org/core.4153 rpm -qa 'emacs*' emacs-w3m-el-1.4.531-0.1.20140421cvs.fc20.noarch emacs-nox-24.3-17.fc20.x86_64 emacs-color-theme-6.6.0-8.fc20.noarch emacs-common-24.3-17.fc20.x86_64 emacs-apel-10.8-6.fc20.noarch emacs-common-w3m-1.4.531-0.1.20140421cvs.fc20.noarch emacs-24.3-17.fc20.x86_64 emacs-filesystem-24.3-17.fc20.noarch emacs-git-1.9.3-1.fc20.noarch emacs-w3m-1.4.531-0.1.20140421cvs.fc20.noarch emacs-el-24.3-17.fc20.noarch I'm emailing the desktop file to jchaloup. The only resolution so far is emacs won't crash during garbage collecting. Lets wait for another crash on startup. Rawhide: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20140804/1327615.html F21: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20140804/1327767.html F20: https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20140804/1327770.html From upstream: Author: Andreas Schwab <schwab> 2014-07-29 10:08:04 Committer: Andreas Schwab <schwab> 2014-07-29 10:08:04 Parent: e9758e4824ab6d79040d7275e191ecf8424fec1b (Fix another part of bug #18035 with redisplay of line-prefix and linum-mode.) Child: fb94658bfca2d0bbaf5af2a2ec766bd06f7803f4 (Fix hscroll of R2L lines that begin with a TAB or another wide glyph.) Branches: emacs-24, remotes/origin/emacs-24, remotes/origin/master, remotes/origin/trunk Follows: emacs-24.3.92 Precedes: Fixes: debbugs:18140 * macros.c (Fstart_kbd_macro): Initialize kbd_macro_ptr and kbd_macro_end together with kbd_macro_buffer. emacs-24.3-22.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/emacs-24.3-22.fc20 Package emacs-24.3-22.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing emacs-24.3-22.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-9169/emacs-24.3-22.fc20 then log in and leave karma (feedback). emacs-24.3-22.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |