From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3)
Description of problem:
M-x ispell-buffer crashes emacs, if .emacs file contains a line with a
very large line-number-display-limit setting
Version-Release number of selected component (if applicable):
emacs-21.3-21.FC2, emacs-common-21.3-21.FC2, emacs-leim-21.3-21.FC2
Steps to Reproduce:
1. Create ~/.emacs, that contains a single line
(setq line-number-display-limit-width 99999999)
2. Start emacs
3. Type in a line into emacs, right into *scratch* buffer. My line was:
alsdkf;lakdf ;lakdf;alkf ;asldf;lakdf
4. Hit M-x ispell-buffer
5. Go through the words in the line using "space" key
6. Observe the crash
7. Remove a couple of '9's from ~/.emacs
8. Repeat the steps 2--5. Observe NO crash instead of step 6
Actual Results: Emacs window disappeared. The following was output to
the shell prompt, from which emacs was started:
Warning: Cannot convert string "fontset-18" to type FontStruct
Fatal error (6).Aborted
Expected Results: Emacs window should have stayed alive. An error
message warning on too high a parameter for
ispell-buffer-display-limit should have been visible somewhere
A cup of hot coffee should have appeared on my desk.
emacs' *Messages* window:
For information about the GNU Project and its goals, type C-h C-p.
Reproduced - this still happens with current cvs emacs too.
Do you see this kind of crashing with saner values of
Additional note: emacs also often also crashes when doing completions.
Eg "M-x c Tab" causes a reproducible crash.
Created attachment 112846 [details]
Still happens with emacs-22.0.50-0.20050714 snapshot.
Does it happen with sane values of line-number-display-limit-width?
(In reply to comment #5)
> Still happens with emacs-22.0.50-0.20050714 snapshot.
> Does it happen with sane values of line-number-display-limit-width?
Please, see items 7 and 8 on the initial bug report in "Bug Comments" section
Oh, yes thanks. Based on that I propose closing then.
BTW this was reported on emacs-devel with no response:
But if you're not enable to produce with vanilla emacs built with from
the upstream tarball, please re-open.
> BTW this was reported on emacs-devel with no response:
Sorry there was one response saying he couldn't reproduce.
(In reply to comment #7)
> Oh, yes thanks. Based on that I propose closing then.
I think emacs should NOT be crashing even if the parameter in the .emacs file is
unreasonably high. As I suggested in the bug report, execution of such a command
should print an error message some how, but not crash the editor. I think the
present behavior is a bug.
I agree it shouldn't crash and if you can help to get a patch
to fix this I would be happy to include it. I don't know if an error
message needs to appear, it should "just work" or ignore very large
values: perhaps that would be a suitable workaround?
Anyway I recommend getting this fixed in cvs emacs first by
discussing it on emacs-devel list.