From: handa@gnu.org (K. Handa)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17881@debbugs.gnu.org, dmantipov@yandex.ru, yamaoka@jpl.org
Subject: bug#17881: 24.4.50; decoding by emacs-mule hangs up
Date: Wed, 02 Jul 2014 00:44:59 +0900 [thread overview]
Message-ID: <87tx71dqx0.fsf@gnu.org> (raw)
In-Reply-To: <83wqby4d8m.fsf@gnu.org> (message from Eli Zaretskii on Mon, 30 Jun 2014 18:40:41 +0300)
In article <83wqby4d8m.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> Fixed in trunk revision 117451.
Thank you for the quick fix!
But, considering the usage of coding->charbuf, I think the
following fix is better. It always allocates 16 units more
in coding->charbuf. So, as far as it doesn't reach
MAX_CHARBUF_SIZE, decoding routines never stop by
insufficient coding->charbuf. I'm going to install it as
soon as I finish several tests.
=== modified file 'src/coding.c'
--- src/coding.c 2014-06-28 13:38:36 +0000
+++ src/coding.c 2014-07-01 15:27:35 +0000
@@ -7266,13 +7266,17 @@
}
#define MAX_CHARBUF_SIZE 0x4000
-#define MIN_CHARBUF_SIZE 0x10
+/* How many units decoding functions expect in coding->charbuf at
+ most. Currently, decode_coding_emacs_mule expects the following
+ size, and that is the largest value. */
+#define MAX_CHARBUF_EXTRA_SIZE ((MAX_ANNOTATION_LENGTH * 3) + 1)
#define ALLOC_CONVERSION_WORK_AREA(coding, size) \
do { \
- int units = ((size) > MAX_CHARBUF_SIZE ? MAX_CHARBUF_SIZE \
- : (size) < MIN_CHARBUF_SIZE ? MIN_CHARBUF_SIZE \
- : size); \
+ int units = (size) + MAX_CHARBUF_EXTRA_SIZE; \
+ \
+ if (units > MAX_CHARBUF_SIZE) \
+ units = MAX_CHARBUF_SIZE; \
coding->charbuf = SAFE_ALLOCA ((units) * sizeof (int)); \
coding->charbuf_size = (units); \
} while (0)
next prev parent reply other threads:[~2014-07-01 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 8:27 bug#17881: 24.4.50; decoding by emacs-mule hangs up Katsumi Yamaoka
2014-06-30 10:10 ` Dmitry Antipov
2014-06-30 15:40 ` Eli Zaretskii
2014-06-30 22:22 ` Katsumi Yamaoka
2014-07-01 15:44 ` K. Handa [this message]
2014-07-01 15:50 ` Eli Zaretskii
2014-07-05 14:13 ` K. 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=87tx71dqx0.fsf@gnu.org \
--to=handa@gnu.org \
--cc=17881@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=yamaoka@jpl.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).