From: Kenichi Handa <handa@m17n.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: h-fujishima@sakura.ad.jp, 2370@emacsbugs.donarmstrong.com
Subject: bug#2370: 23.0.90; decode-coding-region make emacs crash
Date: Thu, 19 Feb 2009 12:56:42 +0900 [thread overview]
Message-ID: <E1La01i-0005wg-DP@etlken> (raw)
In-Reply-To: <87d4dfqg5h.fsf@cyd.mit.edu> (message from Chong Yidong on Wed, 18 Feb 2009 22:06:34 -0500)
In article <87d4dfqg5h.fsf@cyd.mit.edu>, Chong Yidong <cyd@stupidchicken.com> writes:
> Kenichi Handa <handa@m17n.org> writes:
> > I found two bugs related to this problem, and just installed
> > a fix for one of them. Now the above specific problem
> > should be fixed. I'll keep on workning to fix the other bug
> > to make the decoding more robust.
> Thanks. I think decode_coding should also verify the size of the
> unprocessed bytes before writing them to coding->carrover. This way,
> future bugs of this sort will not cause memory corruption (which might
> be a security concern). What's your opinion?
Yes. I'm going to add such a check.
But it doesn't solve the underlying problem of handling too
long (and wrong) composition sequence in iso-2022 decoding.
Solving it requires a little bit more time.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-02-19 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 0:17 bug#2370: 23.0.90; decode-coding-region make emacs crash Chong Yidong
2009-02-19 2:46 ` Kenichi Handa
2009-02-19 3:06 ` Chong Yidong
2009-02-19 3:56 ` Kenichi Handa [this message]
2009-02-19 4:14 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 3:39 Hiroshi Fujishima
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=E1La01i-0005wg-DP@etlken \
--to=handa@m17n.org \
--cc=2370@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=h-fujishima@sakura.ad.jp \
/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).