Subject: Re: bug#76237: 31.0.50; feature/igc: crash #1, 2025-02-12

From: Pip Cet <[email-masked]>
Date: Thu, 13 Feb 2025 14:12:23 +0000

"Oliver Reiter" <[email-masked]> writes:

> Pip Cet <[email-masked]> writes:
>
>> (gdb) p main_thread.s.bc
>>
>> then
>>
>> (gdb) p bc_next_frame (main_thread.s.bc.fp)
>>
>
> (gdb) p main_thread.s.bc
> $1 = {fp = 0x7fffdf3ff710, stack = 0x7fffdf3ff010 "", stack_end = 0x7fffdf7ff010 ""}
> (gdb) p bc_next_frame (main_thread.s.bc.fp)
> You can't do that without a process to debug.

(gdb) p main_thread.s.bc.fp->next_stack

might work.

>> try p *(struct Lisp_String *)0x00007fffec69dd20, maybe
>>
> (gdb) p *(struct Lisp_String *)0x00007fffec69dd20
> $2 = {gc_header = {v = 21508862745, gcaligned = 25 '\031'}, u = {s = {size = 18, size_byte = -1,
>       intervals = 0x0, data = 0x7fffec69e138 "\n\n(fn FORM FULL-P)"}, next = 0x12,
>     gcaligned = 18 '\022'}}

Okay, that's probably internal-macroexpand-for-load.

Still investigating the potential unmarked bytecode stack issue.

Thanks!

Pip