From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 63711@debbugs.gnu.org
Subject: bug#63711: 30.0.50; Crash in xdisp.c when it->string is 0x0
Date: Thu, 25 May 2023 10:34:02 +0300 [thread overview]
Message-ID: <83ilcgn9ud.fsf@gnu.org> (raw)
In-Reply-To: <m35y8hx6wo.fsf@fitzsim.org> (message from Thomas Fitzsimmons on Thu, 25 May 2023 02:27:19 -0400)
> From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
> Date: Thu, 25 May 2023 02:27:19 -0400
>
> I have been having long-running Emacs sessions crash, rarely, and I
> finally caught one case in GDB. Full backtraces attached. I don't know
> how it->string becomes 0x0, but it looks like SCHARS (it->string) then
> attempts to dereference the null pointer. I'll keep the session running
> in case there is anything else someone wants me to check.
Thanks, but with an optimized build and without a recipe to reproduce
this, it will be hard to debug this. Still, I ask you below to
produce some values from GDB in the hope that this would give some
ideas.
(gdb) p pos->overlay_string_index
(gdb) p it->current.overlay_string_index
(gdb) p it->sp
(gdb) p it->method
(gdb) p it->string
(gdb) xtype
If GDB says that the last command "xtype" is not known, type:
(gdb) source /path/to/emacs/src/.gdbinit
(gdb) p it->string
(gdb) xtype
next prev parent reply other threads:[~2023-05-25 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 6:27 bug#63711: 30.0.50; Crash in xdisp.c when it->string is 0x0 Thomas Fitzsimmons
2023-05-25 7:34 ` Eli Zaretskii [this message]
2023-05-25 13:02 ` Thomas Fitzsimmons
2023-05-25 13:35 ` Eli Zaretskii
2023-05-25 13:50 ` Thomas Fitzsimmons
2023-05-25 15:11 ` Eli Zaretskii
2023-05-25 15:25 ` Thomas Fitzsimmons
2023-05-25 15:54 ` Eli Zaretskii
2023-05-25 17:43 ` Thomas Fitzsimmons
2023-05-25 17:52 ` Eli Zaretskii
2023-05-25 18:12 ` Thomas Fitzsimmons
2023-06-01 3:19 ` Thomas Fitzsimmons
2023-06-01 6:29 ` Eli Zaretskii
2023-06-01 11:52 ` Thomas Fitzsimmons
2023-08-03 17:40 ` Thomas Fitzsimmons
2023-08-03 18:34 ` Eli Zaretskii
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=83ilcgn9ud.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63711@debbugs.gnu.org \
--cc=fitzsim@fitzsim.org \
/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).