From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: lekktu@gmail.com, 21822@debbugs.gnu.org, jwiegley@gmail.com
Subject: bug#21822: 25.0.50; emacs_backtrace.txt
Date: Wed, 4 Nov 2015 11:08:40 -0800 (PST) [thread overview]
Message-ID: <31935e4b-2771-4437-b6c0-5f4b1dc0eac3@default> (raw)
In-Reply-To: <<83oaf9u0n8.fsf@gnu.org>>
> It's a nice program that can display any character you want, and also
> can analyze font coverage on your system.
> http://www.babelstone.co.uk/Software/BabelMap.html
Yes, I saw that. I can't get to it from behind the company firewall, as that site is flagged as having a history of security problems. Might try it later, outside the firewall.
> It's the best way I know of to find out which fonts Emacs might have
> tried to use for displaying that character. Armed with that
> knowledge, I might be able to reproduce your crash and fix it.
OK.
> > Shouldn't it be enough to know that Emacs crashed when given
> > a char that it cannot show in the given font? I didn't choose
> > the font - emacs -Q chose it.
>
> The fonts Emacs choses depend on the fonts available on your system.
> I cannot know which fonts you have that cover this character, and
> Emacs doesn't crash for me (nor for Juanma) when we try your recipe.
>
> Assuming you do want the reason for this crash be identified and
> fixed, please help us by providing the information I asked for.
Understood.
next parent reply other threads:[~2015-11-04 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<cd51c877-abad-452c-ad8f-e461f129deaf@default>
[not found] ` <<83oaf9u0n8.fsf@gnu.org>
2015-11-04 19:08 ` Drew Adams [this message]
2015-12-30 10:53 ` bug#21822: 25.0.50; emacs_backtrace.txt Lars Magne Ingebrigtsen
2015-12-30 17:15 ` Drew Adams
[not found] <<d0e2b21f-e168-48e5-89c0-d1686f55093b@default>
[not found] ` <<83pozpu2ic.fsf@gnu.org>
2015-11-04 17:11 ` Drew Adams
2015-11-04 17:36 ` Eli Zaretskii
[not found] <<c0768eea-0152-4b93-9af3-9de1a02d5a0a@default>
[not found] ` <<m2h9l2dee0.fsf@newartisans.com>
[not found] ` <<20f184b5-6966-4ec7-a470-fddd84e6eddb@default>
[not found] ` <<CAAeL0SRuSZYV++jpiZr2Ye18j5cagJg92ELqODb+Zu8Ewx8_Kg@mail.gmail.com>
[not found] ` <<83y4edu65v.fsf@gnu.org>
2015-11-04 16:37 ` Drew Adams
2015-11-04 16:51 ` Juanma Barranquero
2015-11-04 17:08 ` Drew Adams
2015-11-04 16:56 ` Eli Zaretskii
2015-11-03 19:52 Drew Adams
2015-11-03 20:19 ` John Wiegley
2015-11-03 20:26 ` Drew Adams
2015-11-04 8:03 ` Juanma Barranquero
2015-11-04 15:37 ` Eli Zaretskii
2015-12-30 17:15 ` Drew Adams
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=31935e4b-2771-4437-b6c0-5f4b1dc0eac3@default \
--to=drew.adams@oracle.com \
--cc=21822@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.com \
--cc=lekktu@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 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).