From: handa <handa@gnu.org>
To: jamesmikedupont@googlemail.com
Cc: 27446@debbugs.gnu.org
Subject: bug#27446: 25.1; Crashing on rendering of Font
Date: Sat, 24 Jun 2017 13:03:25 +0900 [thread overview]
Message-ID: <87vanmxcaa.fsf@gnu.org> (raw)
In-Reply-To: <83bmpfum7h.fsf@gnu.org> (message from Eli Zaretskii on Fri, 23 Jun 2017 11:45:06 +0300)
In article <83bmpfum7h.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
[...]
> > It shows line 2306, I was scrolling down.
> Thanks. CC'ing Handa-san, in the hope that he could look into this
> issue.
The file has hebrew, devanagari, gothic, Armenian charactes at around
the line 2306. But, I can't reproduce the crash. Perhaps we are using
different fonts.
> > ii libotf0 0.9.13-3
The officially released version is 0.9.13 but the code in the CVS
repository contains several bug fixes. So, could you please try this?
1. Get the newer version by:
% cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/m17n co libotf
2. Install it by:
% cd libotf
% ./autogen.sh
% ./configure --prefix /usr
% make
% sudo make install
If that is difficult, please install the package libotf0-dbg (libotf
libraries and debugging symbols) and show me the backtrace.
---
K. Handa
handa@gnu.org
next prev parent reply other threads:[~2017-06-24 4:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 11:38 bug#27446: 25.1; Crashing on rendering of Font Mike Dupont
2017-06-22 12:14 ` bug#27446: attachments Mike Dupont
2017-06-22 15:08 ` bug#27446: 25.1; Crashing on rendering of Font Eli Zaretskii
2017-06-23 0:23 ` Mike Dupont
2017-06-23 8:45 ` Eli Zaretskii
2017-06-24 4:03 ` handa [this message]
2017-06-24 6:30 ` Eli Zaretskii
2017-06-24 17:32 ` Mike Dupont
2017-06-27 14:57 ` handa
2017-06-28 0:16 ` Mike Dupont
2019-11-04 9:27 ` Stefan Kangas
2019-12-05 11:13 ` Stefan Kangas
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=87vanmxcaa.fsf@gnu.org \
--to=handa@gnu.org \
--cc=27446@debbugs.gnu.org \
--cc=jamesmikedupont@googlemail.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 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).