bug#53497: 29.0.50; native-compile after restarting Emacs

[Arash Esbati <arash@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

> You mean, the breakpoint in maybe_defer_native_compilation never
> breaks?  That in itself is probably a sign of some problem.

This is what I do and see:

-> gdb ./emacs RET
GNU gdb (GDB) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
[...]
Reading symbols from ./emacs...
(gdb) break maybe_defer_native_compilation RET
Breakpoint 1 at 0x400241af0: file comp.c, line 5104.
(gdb) run -Q RET
Starting program: Z:\pathto\bin\emacs.exe -Q
[New Thread 9392.0x3f84]
[New Thread 9392.0x5758]
[New Thread 9392.0x1d48]
[New Thread 9392.0x53e8]
[New Thread 9392.0x51b0]

Thread 1 hit Breakpoint 1, maybe_defer_native_compilation (function_name=0xffff81f161684338, definition=0x1e782a44035) at comp.c:5104
5104      if (!load_gccjit_if_necessary (false))
(gdb)

'Thread 1 hit Breakpoint 1' starts when I try to 'C-x C-f' a .tex file
in Emacs.  And then I can use n, s within the debugger.  But I don't get
any error and such.  Does this make sense to you?  I'm not really
familiar with GDB.

>> I suggest I close this report for now and dig further, I can re-open
>> once I have something new.
>> 
>> OK for you?  Thanks again to you all.
>
> There's no need to close it right away, unless you can no longer
> reproduce the issue.  I'd prefer to close when we either understand
> the reasons or the problem goes away by itself and becomes
> unreproducible.

Fine with me.  Currently, I can reproduce it reliably.

Best, Arash