From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50096@debbugs.gnu.org
Subject: bug#50096: args-out-of-range in redisplay_internal
Date: Tue, 17 Aug 2021 21:51:36 +0300 [thread overview]
Message-ID: <87eearx5tz.fsf@mail.linkov.net> (raw)
In-Reply-To: <83mtpf6hjb.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Aug 2021 21:40:56 +0300")
> So we are in the wrong (empty) buffer? Or did someone delete the
> buffer's text under our feet? What does this show:
>
> (gdb) p object->name_
> (gdb) xstring
> (gdb) p current_buffer->name_
> (gdb) xstring
(gdb) p XBUFFER (object)->name_
$7 = XIL(0x7f015341fb84)
(gdb) xstring
$8 = (struct Lisp_String *) 0x7f015341fb80
" *Minibuf-0*"
(gdb) p current_buffer->name_
$9 = XIL(0x7f015341fb84)
(gdb) xstring
$10 = (struct Lisp_String *) 0x7f015341fb80
" *Minibuf-0*"
PS: Some commit between e2eb58c487 and 31ab12e261 broke that,
but maybe this is not important because these commits
just changed the length of the git command by adding ":(literal)",
and length change maybe exposed some other problem.
next prev parent reply other threads:[~2021-08-17 18:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 16:06 bug#50096: args-out-of-range in redisplay_internal Juri Linkov
2021-08-17 17:18 ` Eli Zaretskii
2021-08-17 17:30 ` Juri Linkov
2021-08-17 17:51 ` Juri Linkov
2021-08-17 18:16 ` Eli Zaretskii
2021-08-17 18:24 ` Juri Linkov
2021-08-17 18:40 ` Eli Zaretskii
2021-08-17 18:51 ` Juri Linkov [this message]
2021-08-17 19:00 ` Eli Zaretskii
2021-08-18 7:42 ` Juri Linkov
2021-08-18 12:18 ` Eli Zaretskii
2021-08-18 16:32 ` Juri Linkov
2021-08-18 17:01 ` Eli Zaretskii
2021-08-18 18:07 ` Eli Zaretskii
2021-08-19 7:17 ` Juri Linkov
2021-08-19 8:12 ` Eli Zaretskii
2021-08-19 12:39 ` Eli Zaretskii
2021-08-20 7:09 ` Juri Linkov
2021-08-20 7:49 ` Eli Zaretskii
2021-08-19 7:32 ` 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=87eearx5tz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=50096@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).