[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Access violation (probably in insert-file-contents)
From: |
David Kastrup |
Subject: |
Re: Access violation (probably in insert-file-contents) |
Date: |
17 Feb 2003 18:47:00 +0100 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 |
"John K. Hohm" <jhohm@acm.org> writes:
> This bug report will be sent to the Free Software Foundation,
> not to your local site managers!
> Please write in English, because the Emacs maintainers do not have
> translators to read other languages for them.
>
> Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
> and to the gnu.emacs.bug news group.
>
> In GNU Emacs 21.2.1 (i386-msvc-nt5.1.2600)
> of 2002-03-19 on buffy
> configured using `configure --with-msvc (12.00)'
> Important settings:
> value of $LC_ALL: nil
> value of $LC_COLLATE: nil
> value of $LC_CTYPE: nil
> value of $LC_MESSAGES: nil
> value of $LC_MONETARY: nil
> value of $LC_NUMERIC: nil
> value of $LC_TIME: nil
> value of $LANG: ENU
> locale-coding-system: iso-latin-1
> default-enable-multibyte-characters: t
>
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
>
> Running the i386 binary release of GNU Emacs 21.2.1 on Windows XP SP1
> with this command:
>
> c:\emacs\bin\emacs -q crashme.txt
>
> or simply calling find-file interactively (via C-x C-f) on the file
> crashme.txt causes an access violation at 0x01084be3 reading
> 0x00000020. WinDbg seems to think that address is
> 'temacs!coding_restore_composition+6e'. I tried the elisp debugger,
> and the last function it shows is insert-file-contents.
Same here with the given file on latest CVS Emacs on Linux. I can
corroborate that the Lisp traceback (xbacktrace) will indicate
insert-file-contents to be the likely culprit.
The C traceback is useless, unfortunately, so I can't say much there.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum