bug#70914: 29.3; Crashes often on Windows

["Simen Endsjø" <simendsjo@gmail.com>]

> Thanks.  Nothing really new.  However, seeing Gdiplus.dll there, a
> stab in the dark: what if you start Emacs like this:
>
  > emacs --eval "(setq-default w32-use-native-image-API nil)"
>
> Do you still see these crashes if you start Emacs like that?

Yes, I get the same errors:

Reading symbols from
D:\tmp\emacs-bug-70914\emacs-no-native-compilation-o0\simendsjo-build\bin\emacs.exe...
(gdb) run --init-directory=d:/.emacs.d --eval "(setq-default
w32-use-native-image-API nil)"
Starting program:
D:\tmp\emacs-bug-70914\emacs-no-native-compilation-o0\simendsjo-build\bin\emacs.exe
--init-directory=d:/.emacs.d --eval "(setq-default
w32-use-native-image-API nil)"
(...)
Thread 1 received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()0

On Sat, May 18, 2024 at 9:35 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Simen Endsjø <simendsjo@gmail.com>
> > Date: Sat, 18 May 2024 20:36:39 +0200
> > Cc: acorallo@gnu.org, 70914@debbugs.gnu.org
> >
> > Thread 1 received signal SIGSEGV, Segmentation fault.
> > 0x0000000000000000 in ?? ()
> > (gdb)rthread apply all bt
>
> Thanks.  Nothing really new.  However, seeing Gdiplus.dll there, a
> stab in the dark: what if you start Emacs like this:
>
>   emacs --eval "(setq-default w32-use-native-image-API nil)"
>
> Do you still see these crashes if you start Emacs like that?