Timeline for How can I debug random Emacs server crashes?
Current License: CC BY-SA 3.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2020 at 17:03 | comment | added | Scott Weldon | @jue: I've had an instance of Emacs launched with -Q running since my last comment, and during that ~2 weeks it hasn't crashed, while my main instance has crashed at least 6 times, and the Docker instance at least 4. I just noticed that I didn't actually run (server-start) this time, but as I mentioned in my question, Emacs has crashed even without that, so I don't think that should make a difference. | |
| May 7, 2020 at 18:04 | comment | added | Scott Weldon | And yes, I'm still getting these crashes 5 years (!) later. | |
| May 7, 2020 at 18:02 | comment | added | Scott Weldon | @jue: Yes, multiple versions of Emacs, multiple computers (a desktop and a laptop), with and without --daemon, all crashed. I actually don't remember now if I have confirmed a crash with -Q, I'll check my notes and/or try it again. I've upgraded my Debian install by at least one release since this question, and I've even had a crash when running this Docker image. | |
| May 7, 2020 at 17:52 | comment | added | Scott Weldon | My apologies for the delay, but thanks all for all the help and suggestions so far. I've had other priorities that have prevented me from looking at this, but I'll try to find the time to work on this again eventually. | |
| Apr 10, 2020 at 1:18 | answer | added | db48x | timeline score: 2 | |
| Oct 15, 2017 at 20:12 | comment | added | Drew | A crash indicates an Emacs bug. Why don't you file a bug report so that Emacs maintainers take a look at it and work with you to understand it better and fix it? You can point to this SE question, but the report itself should include most of the relevant information that you've gathered. M-x report-emacs-bug. | |
| Jun 3, 2017 at 10:35 | comment | added | jue | My comment above: typo: s/could it we/Could it be/. Also did you try emacs24 (version 24.5) from jessie-backports repository?. | |
| Sep 28, 2016 at 2:22 | comment | added | TomRoche | FWIW (1) I have run Emacs versions=23-24 on Debian for several years without encountering this problem. (2) For most of that time I ran emacs --debug-init &, now I'm running emacs --daemon --debug-init & , but (3) ... latter can be problematic, see emacs.stackexchange.com/q/27376/5444 | |
| Sep 6, 2016 at 17:39 | comment | added | xmonk | Read emacs-24/DEBUG it explains the process the developers recommend for debugging emacs. If your emacs is unresponsive you could try attaching gdb to the process and inspect it's state gdb --pid with the emacs instance pid should get you more info. Also if you haven't tried it yet, try running emacs --debug-init and/or adding (autoload 'debug "debug" "emacs debugger") (setq debug-on-error t) to your .emacs file. | |
| Dec 19, 2015 at 21:50 | history | edited | Drew | edited tags | |
| Jun 1, 2015 at 19:27 | comment | added | Lompik | Any luck with M-x report-emacs-bug ? There should be plenty of information for them to help you. I am not able to reproduce this myself. | |
| Jun 1, 2015 at 15:23 | comment | added | Scott Weldon | @Lompik I've edited my question (again). | |
| Jun 1, 2015 at 15:21 | history | edited | Scott Weldon | CC BY-SA 3.0 | added 160 characters in body |
| Jun 1, 2015 at 15:14 | history | edited | Scott Weldon | CC BY-SA 3.0 | added 160 characters in body |
| May 22, 2015 at 15:20 | history | edited | Scott Weldon | CC BY-SA 3.0 | added 610 characters in body |
| May 19, 2015 at 17:39 | comment | added | Lompik | reddit.com/r/emacs/comments/2ans0z/… bugs.launchpad.net/ubuntu/+source/emacs23/+bug/543611 | |
| May 19, 2015 at 15:26 | comment | added | Scott Weldon | Yes, I will try compiling Emacs myself. If that doesn't work, I'll probably launch with emacs -Q and then leave that running over the weekend and see if the crash happens. | |
| May 19, 2015 at 15:04 | comment | added | Lompik | Is possible for you compile emacs and/or ty other version. One simple one you'd have to check first : does it also happen with emacs -Q ? I'd say M-x report-emacs-bug and see with the experts. be sure to read line 10 : git.savannah.gnu.org/cgit/emacs.git/tree/etc/DEBUG#n10 | |
| May 18, 2015 at 15:40 | history | edited | Scott Weldon | CC BY-SA 3.0 | added 1007 characters in body |
| May 15, 2015 at 15:26 | comment | added | Scott Weldon | FWIW, launching Emacs and then doing M-x server-start doesn't seem to help, as it just crashed again. Time to launch GDB. | |
| May 13, 2015 at 17:03 | comment | added | Scott Weldon | sudo journalctl -xe returns command not found (I'm currently on Ubuntu). dmesg | grep emacs returns empty. Thanks for the info, I'll take a look at launching it from GDB. | |
| May 13, 2015 at 16:57 | comment | added | Lompik | there should be a trace of something like "emacs dumped core" in sudo journalctl -xe or even dmesg | grep emacs. My point is that is is possible to anlyse the core dump file and get a backtrace. In any case, you could launch emacs from gdb and get a backtrace of the last function called before the the crash. Basically, I would try to get as much info as possible to get rid of the randomness and make it reproducible. This might or not take some time but one it is, M-x report-emacs-bug with your finding. See git.savannah.gnu.org/cgit/emacs.git/tree/etc/DEBUG for details. | |
| May 13, 2015 at 16:19 | comment | added | Scott Weldon | It just dies quietly. All my emacsclient windows disappear, and immediately after that, anything like ps -ef | grep emacs returns empty. | |
| May 13, 2015 at 16:08 | comment | added | Lompik | Just to make it clearer: Does it crashes as in "dumped core" / received segfault or does it freezes (and you have to kill emacs) ? | |
| May 13, 2015 at 15:33 | comment | added | Scott Weldon | Crashed again while running the Lucid toolkit. Unfortunately, it looks like this isn't the problem. I'll try out your other suggestion, and see if it makes a difference if I run Emacs normally and then do M-x server-start. | |
| May 11, 2015 at 3:34 | comment | added | Scott Weldon | Good point. I had seen that warning, but thought it was only a problem when restarting my X session. I'll report back after I've done some testing with the Lucid toolkit. | |
| May 11, 2015 at 3:24 | comment | added | Lompik | I experienced the same. There is a warning that emacs (GTK) might crash when you launch with --daemon option. Not sure if it is related, you could try the lucid toolkit. I now just launch emacs with (server-start) in my init file and get the same client/server behavior. | |
| May 11, 2015 at 1:56 | history | asked | Scott Weldon | CC BY-SA 3.0 |