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 13:43:03 -0400 [thread overview]
Message-ID: <m3zg5s1f4o.fsf@fitzsim.org> (raw)
In-Reply-To: <83353kmmoq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 May 2023 18:54:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
>> Cc: 63711@debbugs.gnu.org
>> Date: Thu, 25 May 2023 11:25:23 -0400
>>
>> > (gdb) prow
>>
>> y=701 x=0 pwid=1287 a+d=18+5=23 phys=16+4=20 vis=23
>> used=(LMargin=0,Text=113,RMargin=0) Hash=258184180
>> start=0 end=0 ENA MODEL
>>
>> > (gdb) pgrow
>>
>> TEXT: 113 glyphs
>> 0 0: CHAR[ ] str=0xf188ab16[0] blev=0,btyp=L w=11 a+d=18+5 face=1
>> 1 11: CHAR[U] str=0x1ccec60[1] blev=0,btyp=L w=11 a+d=18+5 face=1
>> 2 22: CHAR[:] str=0x4e125d0[0] blev=0,btyp=L w=11 a+d=18+5 face=1
>> 3 33: STRETCH[23+18] str=0x1ccecb8[0] w=33 a+d=18+5 face=1
>> 4 66: CHAR[@] str=0x1ccecb8[0] blev=0,btyp=L w=11 a+d=18+5 face=1
>
> This is the mode line: first sign of trouble. We are handling a
> mode-line glyph row as if it were a text row. That cannot lead to
> anything good, ever.
>
>> > (gdb) p first_reusable_row - start_row
>>
>> $22 = 15
>>
>> > (gdb) p first_row_to_display - start_row
>>
>> $23 = 30
>
> So we think that the first glyph row to display is screen line 30
> (zero-based). Is it true that the window was supposed to have only 30
> lines in its body, not 31?
I don't remember, but it does sound plausible that the window displaying
the "js.el" buffer was ~30 lines tall. I was probably working in a
"split-window-below" scenario. I don't know whether it was supposed to
be 30 or 31; maybe there some consistency check I could perform in the
GDB session to nail down the expected value?
Thanks,
Thomas
next prev parent reply other threads:[~2023-05-25 17:43 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 [this message]
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=m3zg5s1f4o.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).