bug#48433: 28.0.50; Emacs Core Dump when trying to visit file

[Sébastien Le Callonnec]

Hi Eli,

On 15/05/2021 12:25, Eli Zaretskii wrote:
(...)
> 
>> (gdb) bt full
>> #0  terminate_due_to_signal (sig=21845, backtrace_limit=1481635280) at
>> emacs.c:399
>> #1  0x000055555571c837 in emacs_abort () at sysdep.c:2282
>> #2  0x000055555573decb in Factive_minibuffer_window () at minibuf.c:231
>>         frames = XIL(0x1f1dad70d)
>>         frame = make_fixnum(23456248280808)
>>         f = 0x55555623e6a5
>>         innermost_MB = XIL(0)
> 
> What is the value of minibuf_level in frame #2?

(gdb) b Factive_minibuffer_window
Breakpoint 2 at 0x1e9e76: file minibuf.c, line 221.
(gdb) run -Q --load ~/init-ido.el
Starting program: /home/sebastien/dev/emacs/src/emacs -Q --load
~/init-ido.el
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff1579640 (LWP 561829)]
[New Thread 0x7ffff0d17640 (LWP 561830)]
[New Thread 0x7fffebfff640 (LWP 561831)]

Thread 1 "emacs" hit Breakpoint 2, Factive_minibuffer_window () at
minibuf.c:221
221     {
(gdb) select-frame 2
(gdb) p minibuf_
minibuf_c_loop_level             minibuf_follows_frame
minibuf_moves_frame_when_opened  minibuf_prompt_width
minibuf_selected_window
minibuf_conform_representation   minibuf_level
minibuf_prompt                   minibuf_save_list
minibuf_window
(gdb) p minibuf_level
$1 = 0


I reported from an older version of Emacs, as the current one is
unusable, but it seems in the meantime this commit seems to have fixed
the issue:

46e4704e2abca4d264a43965f92eab7608211ee6

Regards,
Sébastien.