From: Eli Zaretskii <eliz@gnu.org>
To: Yuchen Guo <yguo@posteo.net>, Po Lu <luangruo@yahoo.com>
Cc: 66416@debbugs.gnu.org
Subject: bug#66416: GDB output from new crash
Date: Thu, 12 Oct 2023 15:31:09 +0300 [thread overview]
Message-ID: <83r0m0t436.fsf@gnu.org> (raw)
In-Reply-To: <87jzrs3x14.fsf@lan> (message from Yuchen Guo on Thu, 12 Oct 2023 11:22:47 +0000)
> From: Yuchen Guo <yguo@posteo.net>
> Cc: 66416@debbugs.gnu.org
> Date: Thu, 12 Oct 2023 11:22:47 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Assuming you still have this session caught in GDB, please type at the
> > GDB prompt:
> >
> > (gdb) fr 8
> > (gdb) p cache
> > (gdb) p ftcrfont_info->metrics[row]
> >
> > and post the results here.
> >
> > Thanks.
>
> #8 ftcrfont_glyph_extents (font=0x3fe60998, glyph=1182, metrics=metrics@entry=0x0) at ftcrfont.c:94
> warning: Source file is more recent than executable.
> 94 if (METRICS_STATUS (cache) == METRICS_INVALID)
> $1 = (struct font_metrics *) 0x12d
> $2 = (struct font_metrics *) 0x1
> quit
Po Lu, any idea what happened here? ftcrfont_info->metrics is clearly
bogus, but how did it happen and why? The argument FONT seems to be
valid.
next prev parent reply other threads:[~2023-10-12 12:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 20:32 bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland Yuchen Guo
2023-10-09 10:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 11:19 ` Eli Zaretskii
2023-10-09 11:24 ` Eli Zaretskii
[not found] ` <87bkd7k6b8.fsf@lan>
2023-10-09 18:45 ` Eli Zaretskii
2023-10-09 19:07 ` Yuchen Guo
2023-10-10 2:30 ` Eli Zaretskii
2023-10-10 5:26 ` Yuchen Guo
2023-10-10 12:08 ` Eli Zaretskii
2023-10-10 12:59 ` Yuchen Guo
2023-10-10 13:40 ` Eli Zaretskii
2023-10-10 16:26 ` Yuchen Guo
2023-10-11 11:31 ` Eli Zaretskii
2023-10-11 12:45 ` Yuchen Guo
2023-10-11 13:12 ` Eli Zaretskii
2023-10-10 4:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 18:44 ` bug#66416: Coredump Yuchen Guo
2023-10-12 7:46 ` bug#66416: GDB output from new crash Yuchen Guo
2023-10-12 8:12 ` Yuchen Guo
2023-10-12 10:23 ` Eli Zaretskii
2023-10-12 11:22 ` Yuchen Guo
2023-10-12 12:31 ` Eli Zaretskii [this message]
2023-10-12 13:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 14:28 ` Yuchen Guo
2023-10-12 14:42 ` Yuchen Guo
2023-10-14 11:00 ` Eli Zaretskii
2023-10-14 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 12:38 ` Eli Zaretskii
2023-10-14 12:40 ` Yuchen Guo
2023-10-14 12:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 14:23 ` Yuchen Guo
2023-10-14 15:40 ` Eli Zaretskii
2023-10-15 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-15 5:54 ` Yuchen Guo
2023-10-12 11:43 ` Yuchen Guo
2023-10-14 19:14 ` bug#66416: 29.1; pgtk build crashes due to ftcrfont Yuchen Guo
2024-04-16 0:27 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87mspui23l.fsf@>
2024-04-16 12:16 ` Eli Zaretskii
2024-04-16 13:13 ` Mattias Engdegård
2024-04-16 14:21 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 13:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 14:19 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83r0m0t436.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66416@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=yguo@posteo.net \
/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).