From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: [BUG] coding.c/decode_coding_iso2022
Date: Fri, 15 Aug 2003 09:42:38 +0900 (JST) [thread overview]
Message-ID: <200308150042.JAA27994@etlken.m17n.org> (raw)
In-Reply-To: <usmo4rvqo.fsf@boost-consulting.com> (message from David Abrahams on Thu, 14 Aug 2003 13:31:59 -0400)
In article <usmo4rvqo.fsf@boost-consulting.com>, David Abrahams <dave@boost-consulting.com> writes:
> Tired of the numerous crashes I've been getting under NT, I
> recompiled emacs with all the runtime checks enabled. I think I'll
> be posting lots of reports.
> The title function uses variable c2 uninitialized during this phase
> of the make process:
> Loading language/devanagari (source)...
> The stack trace is:
> ntdll.dll!77f75a58()
> temacs.exe!failwithmessage(void * retaddr=0x011b5c7f, int crttype=0x00000001, int errnum=0x00000003, const char * msg=0x0111431e) + 0x106 C++
> temacs.exe!_RTC_UninitUse(const char * varname=0x01114900) + 0x9c C++
>> temacs.exe!decode_coding_iso2022() Line 2169 + 0x33c C
It seems that the relevant line is this:
c = DECODE_ISO_CHARACTER (charset, c1, c2);
But, ...
[...]
> Locals at the point of the error:
> c2 0xcccccccc int
> c1 0x0000003b int
> + coding 0x0081f1e4 {type=coding_type_iso2022 eol_type=0x00000001 common_flags=0x00000007 ...} coding_system *
> + source 0x0158da80 ";;; devanagari.el --- Support for Devanagari -*- coding: iso-2022-7bit; no-byte-compile: t -*-
[...]
> + destination 0x0158d2b0 "" unsigned char *
> src_bytes 0x000006b7 int
> dst_bytes 0x00000000 int
> charset1 0xffffffff int
> charset 0x00000000 int
> + src 0x0158da81 ";; devanagari.el --- Support for Devanagari -*- coding: iso-2022-7bit; no-byte-compile: t -*-
[...]
> translation_table 0x41398000 int
> c 0xcccccccc int
> charset0 0x00000000 int
> + src_end 0x0158e137 "" unsigned char *
> + dst_end 0x0158d2b0 "" unsigned char *
> + dst 0x0158d2b0 "" unsigned char *
> + src_base 0x0158da80 ";;; devanagari.el --- Support for Devanagari -*- coding: iso-2022-7bit; no-byte-compile: t -*-
[...]
> safe_chars 0x1137e834 int
As the value of charset is 0, c2 is never referred in the
macro DECODE_ISO_CHARACTER except for as the last argument
to the function translate_char. And in that function also,
as charset is zero, c2 is never referred.
So, I think this is not the reason of the crash of your emacs.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-08-15 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 17:31 [BUG] coding.c/decode_coding_iso2022 David Abrahams
2003-08-14 17:38 ` David Abrahams
2003-08-15 0:42 ` Kenichi Handa [this message]
2003-08-15 2:41 ` David Abrahams
2003-08-15 2:45 ` Kenichi Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308150042.JAA27994@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).