From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 20890@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#20890: master 1233bcb: Work around GC+Cairo bug
Date: Wed, 04 Apr 2018 12:08:26 +0300 [thread overview]
Message-ID: <837epn49v9.fsf@gnu.org> (raw)
In-Reply-To: <878ta34alh.fsf@gmail.com> (message from Robert Pluim on Wed, 04 Apr 2018 10:52:42 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: eggert@cs.ucla.edu, 20890@debbugs.gnu.org
> Date: Wed, 04 Apr 2018 10:52:42 +0200
>
> > Sorry, I don't understand: are you saying that you still get crashes
> > inside ftfont_close, after the above commit? If so, can you please
> > show the backtrace?
>
> Yes.
>
> > (Let's please continue discussing this in the bug report, not here.)
>
> Moved there. Backtrace:
>
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff1f87c68 in FT_List_Find () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
> (gdb) bt
> #0 0x00007ffff1f87c68 in FT_List_Find () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
> #1 0x00007ffff1f87ecf in FT_Done_Size () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
> #2 0x00000000005d5484 in ftcrfont_close (font=0x35fdf60) at ftcrfont.c:176
> #3 0x00000000005502db in cleanup_vector (vector=vector@entry=0x35fdf60) at alloc.c:3194
This is not in ftfont_close, this is in ftcrfont_close.
If you can tell why FT_List_Find crashes, in terms of Emacs variables
and data structures, maybe we can figure out what is going on here.
But in any case, I think we should put the same workaround in
ftcrfont_close as we did in ftfont_close, because the former calls the
latter, and we then risk the situation where we only half-close the
font when ftcrfont_close is called from GC.
Thanks.
next prev parent reply other threads:[~2018-04-04 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180403152442.25413.61540@vcs0.savannah.gnu.org>
[not found] ` <20180403152443.B15F6215A9@vcs0.savannah.gnu.org>
[not found] ` <87a7ukc4zn.fsf@gmail.com>
[not found] ` <83k1tn4h4f.fsf@gnu.org>
2015-06-24 10:26 ` bug#20890: 25.0.50; build from git crashes on startup Robert Marshall
2015-07-26 20:30 ` Paul Eggert
2018-04-03 9:39 ` Robert Pluim
2018-04-03 10:06 ` Eli Zaretskii
2018-04-03 15:03 ` Paul Eggert
2018-04-03 15:13 ` Eli Zaretskii
2018-04-03 15:26 ` Paul Eggert
2018-04-04 8:52 ` bug#20890: master 1233bcb: Work around GC+Cairo bug Robert Pluim
2018-04-04 9:08 ` Eli Zaretskii [this message]
2018-04-04 12:10 ` Robert Pluim
2018-04-04 13:44 ` Eli Zaretskii
2018-04-04 18:00 ` Paul Eggert
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=837epn49v9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20890@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).