From: Eli Zaretskii <eliz@gnu.org>
To: handa <handa@gnu.org>
Cc: 49066@debbugs.gnu.org, rpluim@gmail.com, eggert@cs.ucla.edu,
larsi@gnus.org, mvsfrasson@gmail.com
Subject: bug#49066: 26.3; Segmentation fault on specific utf8 string
Date: Sun, 27 Jun 2021 09:20:41 +0300 [thread overview]
Message-ID: <83tuljq152.fsf@gnu.org> (raw)
In-Reply-To: <87sg14kpkn.fsf@gnu.org> (message from handa on Sun, 27 Jun 2021 11:29:28 +0900)
> From: handa <handa@gnu.org>
> Cc: rpluim@gmail.com, larsi@gnus.org, 49066@debbugs.gnu.org,
> mvsfrasson@gmail.com, eggert@cs.ucla.edu
> Date: Sun, 27 Jun 2021 11:29:28 +0900
>
> So, I tried to restore the old code as the attached patch, and then the
> patched emacs has no problem of rendering the above Bengali string.
Thanks. Robert, Miguel: could you please try this patch and see if it
fixes the problem?
Since we are moving away of m17n-flt, I don't think we should optimize
memory management when m17n-flt is used, especially if that causes
problems. So if the patch fixes the crash, I think we should install
it.
next prev parent reply other threads:[~2021-06-27 6:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 21:07 bug#49066: 26.3; Segmentation fault on specific utf8 string Miguel V. S. Frasson
2021-06-16 21:12 ` Lars Ingebrigtsen
2021-06-17 6:43 ` Eli Zaretskii
2021-06-17 7:43 ` Robert Pluim
2021-06-17 8:13 ` Eli Zaretskii
2021-06-17 13:07 ` Robert Pluim
2021-06-17 13:59 ` Eli Zaretskii
2021-06-17 15:04 ` Eli Zaretskii
2021-06-27 2:29 ` handa
2021-06-27 6:20 ` Eli Zaretskii [this message]
2021-06-27 18:02 ` Paul Eggert
2021-06-27 19:15 ` Eli Zaretskii
2021-06-28 10:56 ` Robert Pluim
2021-06-28 12:05 ` Eli Zaretskii
2021-07-03 2:05 ` handa
2021-07-05 9:28 ` Robert Pluim
2021-07-20 12:23 ` Lars Ingebrigtsen
2021-06-16 21:22 ` bug#49066: file foo Miguel V. S. Frasson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tuljq152.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49066@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=handa@gnu.org \
--cc=larsi@gnus.org \
--cc=mvsfrasson@gmail.com \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.