From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Eli Zaretskii <eliz@gnu.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 09:50:44 -0400 [thread overview]
Message-ID: <m3cz2o34gb.fsf@fitzsim.org> (raw)
In-Reply-To: <835y8gmt3f.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 May 2023 16:35:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
>> Cc: 63711@debbugs.gnu.org
>> Date: Thu, 25 May 2023 09:02:26 -0400
>>
>> > (gdb) p it->sp
>>
>> $11 = 0
>>
>> > (gdb) p it->method
>>
>> $12 = GET_FROM_BUFFER
>
> These last two values are already a sign of trouble, AFAIU. We are
> trying to find an overlay string where there is none. But if that is
> the case, how come pos->overlay_string_index is non-negative? that
> should not happen.
OK, interesting.
>> The session is still open if you want me to check other values.
>
> Do you know what kind of buffer is the current buffer in this case?
> The following command will show some of the buffer text near the
> position that is examined here, to possibly help you figure out the
> buffer:
>
> (gdb) p (*BYTE_POS_ADDR(pos->pos.bytepos))@100
>
> (Here 100 is the number of bytes to display; feel free to use more if
> 100 is insufficient.)
$14 = "\000\000;; js.el --- Major mode for editing JavaScript -*- lexical-binding: t -*-\n\n;; Copyright (C) 2008-"
> Once you do understand what buffer is this, please try to describe the
> overlays at buffer position pos->pos.charpos in that buffer, if there
> are supposed to be any overlays there.
(gdb) p pos->pos.charpos
$16 = 0
So I guess the first 100 characters printed above already shows the
context at pos->pos.charpos? Are those leading zero-bytes expected?
> That position is supposed to be the first position of a screen line,
> i.e. the position of the leftmost character on display in that line.
I was experimenting with font-locking JavaScript. Maybe I put Emacs
into a strange state that way (though it still shouldn't be crashable).
I can't visually inspect the affected window anymore; it was an X11
window, tunneled through an SSH connection which I've since closed.
Thanks,
Thomas
next prev parent reply other threads:[~2023-05-25 13:50 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 [this message]
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=m3cz2o34gb.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=63711@debbugs.gnu.org \
--cc=eliz@gnu.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).