GNU bug report logs -
#39207
28.0.50; crash when sending gnus message
Previous Next
Reported by: Gijs Hillenius <gijs <at> hillenius.net>
Date: Mon, 20 Jan 2020 16:29:02 UTC
Severity: normal
Found in version 28.0.50
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
>>>>> On Tue, 21 Jan 2020 10:06:41 +0100, gijs <at> hillenius.net (Gijs Hillenius) said:
Gijs> Dear Robert et al,
Gijs> I am not sure this will help you any, but here is the output from a gdb
Gijs> session without debug symbols, where I eventually ended up C-g'ing
Gijs> emacs-snapshot, because it was misbehaving on Gnus.
Gijs> Gnus works fine in Debian's Emacs (26.3) (knocks wood), but in this
Gijs> weekend's emacs-snapshot, it is doing the strangest things: selecting
Gijs> the next message in a thread in mail (nnimap), it won't show the
Gijs> message, but jump to a earlier message, (some ten lines or so higher)
Gijs> *and* mark all mail messages below this message as 'moved' (without
Gijs> moving them really). It also adds a new empty line at the end, which
Gijs> when I try to select it, will cause the CPU to go to 100%.
Gijs> In news (nntp) it is impossible to read the next message in a thread, it
Gijs> will simply bounce back to the first message in the thread. Trying to
Gijs> exit gnus will cause emacs to hang.
If you still have this in gdb, can you run 'bt'? (debug symbols would
really help. If you build your own emacs you'll get debug symbols,
although Iʼm surprised your snapshot has been stripped).
Robert
This bug report was last modified 5 years and 173 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.