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, 01 Jun 2023 09:29:23 +0300 [thread overview]
Message-ID: <838rd3elvg.fsf@gnu.org> (raw)
In-Reply-To: <m3zg5jswbn.fsf@fitzsim.org> (message from Thomas Fitzsimmons on Wed, 31 May 2023 23:19:56 -0400)
> From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
> Cc: 63711@debbugs.gnu.org
> Date: Wed, 31 May 2023 23:19:56 -0400
>
> This Emacs run ultimately crashed tonight, but the signature seems
> different.
Crashed for what reason? The information shown by GDB about the
signal which crashed Emacs is missing.
And the place in the source where it crashed looks strange:
INLINE _GL_ATTRIBUTE_CONST bool
pdumper_object_p (const void *obj)
{
#ifdef HAVE_PDUMPER
uintptr_t obj_addr = (uintptr_t) obj; <<<<<<<<<<<<<<<<<<<<<<<
return dump_public.start <= obj_addr && obj_addr < dump_public.end;
#else
(void) obj;
return false;
#endif
}
How can anything in this function crash? The only possible reason I
can think of is C stack overflow (but the number of call-stack frames
is not large enough to justify that). Or maybe another thread
crashed, not the main thread? The information displayed by GDB when
it catches a fatal signal tells that as well.
> The GDB session is still running if you want me to check
> anything. I wasn't doing anything special when this happened. Does the
> backtrace suggest that garbage collection happened during a
> fontification operation?
Yes, this happened inside GC. So it's most probably completely
unrelated to this bug, and so please submit a new bug report with all
the information.
next prev parent reply other threads:[~2023-06-01 6:29 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
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 [this message]
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=838rd3elvg.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).