From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Chong Yidong <cyd@gnu.org>
Cc: Dan Maftei <ninestraycats@gmail.com>, 11964-done@debbugs.gnu.org
Subject: bug#11964: describe-char causes a fatal error (abort trap: 6) in non-windowed mode
Date: Sat, 24 Nov 2012 18:59:54 +0100 [thread overview]
Message-ID: <97BC8D6C-F53B-4E18-9089-B4F8D7E39372@swipnet.se> (raw)
In-Reply-To: <DBE27C2B-FBE4-45E1-80D8-41F5F005895A@swipnet.se>
Hello.
This has been fixed in the trunk.
The problem was that ns-win created fontsets unconditionally during load and that lead to problems when running with -nw, in face_for_char. Shouldn't fontsets/font objects be ignored if the terminal is a non-GUI one?
Jan D.
23 nov 2012 kl. 08:07 skrev Jan Djärv <jan.h.d@swipnet.se>:
> Hello.
>
> 23 nov 2012 kl. 07:26 skrev Chong Yidong <cyd@gnu.org>:
>
>> Jan Djärv <jan.h.d@swipnet.se> writes:
>>
>>> Here is a backtrace. The fontdriver does not have an encode_char
>>> function (it is NULL). But I don't know which driver this is. Lisp
>>> backtrace is broken it seems.
>>
>> Could you do
>>
>> f 1
>> pp face->font->driver->type
>>
>> and see what font driver it is (or if there is one)?
>
> Basically no, because
>
> p face->font->driver
> $3 = (struct font_driver *) 0x3
>
> Uninitialized memory?
>
> Jan D.
>
next prev parent reply other threads:[~2012-11-24 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 22:51 bug#11964: describe-char causes a fatal error (abort trap: 6) in non-windowed mode Dan Maftei
2012-11-05 14:23 ` Chong Yidong
2012-11-05 15:20 ` Jan Djärv
2012-11-23 6:26 ` Chong Yidong
2012-11-23 7:07 ` Jan Djärv
2012-11-23 9:28 ` Chong Yidong
2012-11-24 17:59 ` Jan Djärv [this message]
2012-11-24 18:19 ` Eli Zaretskii
2012-11-25 5:30 ` Chong Yidong
2012-11-25 12:18 ` Jan Djärv
2012-11-25 15:56 ` Eli Zaretskii
2012-11-25 16:16 ` Jan Djärv
2012-11-25 16:34 ` Eli Zaretskii
2012-11-25 17:17 ` Jan Djärv
2012-11-26 3:55 ` Chong Yidong
2012-11-26 17:47 ` Eli Zaretskii
2012-11-05 18:52 ` Dan Maftei
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=97BC8D6C-F53B-4E18-9089-B4F8D7E39372@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=11964-done@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=ninestraycats@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).