From: andrei.elkin--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44502@debbugs.gnu.org
Subject: bug#44502:
Date: Thu, 11 Aug 2022 22:10:12 +0300 [thread overview]
Message-ID: <87edxmha0b.fsf@quad> (raw)
In-Reply-To: <83y1vuoc5s.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Aug 2022 21:41:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: andrei.elkin@pp.inet.fi
>> Cc: 44502@debbugs.gnu.org
>> Date: Thu, 11 Aug 2022 21:19:06 +0300
>>
>> (gdb) p window
>> $4 = XIL(0x55555b038855)
>> (gdb) xwindow
>> $5 = (struct window *) 0x55555b038850
>> 124x1+0+80
>> (gdb) print XWINDOW(window)->contents
>> $6 = XIL(0x7fffea1bd07d)
>> (gdb) xbuffer
>> $7 = (struct buffer *) 0x7fffea1bd078
>> 0x7fffea4aedc1 " *Minibuf-0*"
>> (gdb) print selected_window
>> $8 = XIL(0x55555b038645)
>> (gdb) xwindow
>> $9 = (struct window *) 0x55555b038640
>> 124x80+0+0
>> (gdb) print XWINDOW(selected_window)->contents
>> $10 = XIL(0x5555577f9475)
>> (gdb) xbuffer
>> $11 = (struct buffer *) 0x5555577f9470
>> 0x555559788ff0 "magit: A<10.6>"
>
> Do you remember what were you doing when this assertion violation
> happened?
Something like
C-u M-x shell
>
>
> Also, are you using a separate minibuffer frame?
No
next prev parent reply other threads:[~2022-08-11 19:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 13:27 bug#44502: 28.0.50; Emacs crash using new frame Andy Moreton
2020-11-07 13:51 ` Andy Moreton
2020-11-07 14:05 ` Eli Zaretskii
2020-11-08 13:37 ` Alan Mackenzie
2020-11-08 15:15 ` Eli Zaretskii
2020-11-08 15:36 ` Andy Moreton
2021-09-08 9:52 ` Lars Ingebrigtsen
2022-08-10 13:26 ` bug#44502: andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-10 15:49 ` bug#44502: Eli Zaretskii
2022-08-11 18:19 ` bug#44502: andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11 18:41 ` bug#44502: Eli Zaretskii
2022-08-11 19:10 ` andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-12 6:27 ` bug#44502: Eli Zaretskii
2022-08-12 8:34 ` bug#44502: Alan Mackenzie
2022-08-12 10:24 ` bug#44502: andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 14:30 ` bug#44502: Alan Mackenzie
2022-08-19 10:45 ` bug#44502: Eli Zaretskii
2022-08-19 13:05 ` bug#44502: Alan Mackenzie
2022-08-19 13:20 ` bug#44502: Eli Zaretskii
2022-08-19 15:12 ` bug#44502: Alan Mackenzie
2022-08-19 16:10 ` bug#44502: andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87edxmha0b.fsf@quad \
--to=bug-gnu-emacs@gnu.org \
--cc=44502@debbugs.gnu.org \
--cc=andrei.elkin@pp.inet.fi \
--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).