bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Hi emacs,

When I editing my ~/.config/emacs/init.el file, Emacs will raise a fatal
error frequenly when flymake-mode enabled.

With a few hours debug, I found that it's related to flymake-mode and
Borg( A package manager writed by Jonas Bernoulli).

Borg repos: https://github.com/emacscollective/borg


This issue can be fixed by disable flymake-mode or without Borg, just
use package.el to install packages.

It would be nice if I can use Borg with flymake-mode. I am not sure this
bug if from Borg or flymake-mode or Emacs itself, so I report it here.

Steps to reproduce:

1. Make sure you have Emacs 29 installed, I build it from emacs-29
branch:

https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29&id=2569ede9c496bb060e0b88428cb541088aaba1f9

2. Install Borg by the emacs.g seed
```
git clone git@github.com:emacscollective/emacs.g.git ~/.config/emacs
cd ~/.config/emacs
make bootstrap-borg
make bootstrap
```
By default, It use ssh, if you want to use https, you can configure like
this:
```
git config --global url.https://github.com/.insteadOf git@github.com:
git config --global url.https://git.sr.ht/.insteadOf git@git.sr.ht:
```

3. Start Emacs and open the ~/.config/emacs/init.el file
```
C-x, C-f ~/.config/emacs/init.el
```
4. Enable flymake-mode by M-x, flymake-mode
5. Add some new blank line in the init.el buffer and then save the
buffer with C-x, C-s

6. Now you will see the fatal error popup window with below message:

Emacs Abort Dialog
A fatal error has occurred!
Would you like to attach a debugger?

Select:
YES -- to debug Emacs, or
NO -- to abort Emacs and produce a backtrace
      (emacs backtracetxt in current directory).
(type "gdb -p <emacs-PID>" and
"continue" inside GDB before clicking YES.)


7. I follow the error message to use GDB debug and got the infomation as
below, maybe it can help you to find the bug:

➜ ~  ps -name emacs

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     62    81.07      92.62       9.23    7544   1 emacs

➜ ~  mingw

Aqua@DESKTOP-CIHAF12 MINGW64 ~
$ gdb -p 7544
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 7544
[New Thread 7544.0x3c50]
[New Thread 7544.0x49bc]
[New Thread 7544.0x1e94]
[New Thread 7544.0x3f3c]
[New Thread 7544.0x4370]
Reading symbols from C:\opt\emacs\bin\emacs.exe...
(gdb) c
Continuing.
[Thread 7544.0x4370 exited with code 0]
[New Thread 7544.0x1b60]
[New Thread 7544.0x2edc]
[New Thread 7544.0x4d6c]
[New Thread 7544.0x4474]
[Thread 7544.0x2edc exited with code 0]
[Thread 7544.0x1b60 exited with code 0]
[New Thread 7544.0x39fc]
[New Thread 7544.0x3a9c]
[Thread 7544.0x4474 exited with code 0]
[Thread 7544.0x4d6c exited with code 0]
[New Thread 7544.0x2050]
[New Thread 7544.0x4da8]
[Thread 7544.0x3a9c exited with code 0]
[Thread 7544.0x39fc exited with code 0]
[Thread 7544.0x4da8 exited with code 0]
[Thread 7544.0x2050 exited with code 0]
[New Thread 7544.0x42f4]
[New Thread 7544.0xc9c]
[New Thread 7544.0x1a70]
[Thread 7544.0x1a70 exited with code 1]
[New Thread 7544.0x462c]
[Thread 7544.0x462c exited with code 1]
[New Thread 7544.0x3198]
[Thread 7544.0x3198 exited with code 1]
[New Thread 7544.0x53b4]
[New Thread 7544.0x256c]
[New Thread 7544.0x304]
[New Thread 7544.0x10a4]
[Thread 7544.0x256c exited with code 0]
[Thread 7544.0x53b4 exited with code 0]
[New Thread 7544.0x4c3c]
[Thread 7544.0x4c3c exited with code 1]
[New Thread 7544.0x874]
[Thread 7544.0x874 exited with code 1]
[New Thread 7544.0x4964]
[Thread 7544.0x4964 exited with code 1]
[New Thread 7544.0x2328]
[New Thread 7544.0x3a0c]
[Thread 7544.0x10a4 exited with code 0]
[Thread 7544.0x304 exited with code 0]
[Thread 7544.0xc9c exited with code 0]
[Thread 7544.0x42f4 exited with code 0]
[New Thread 7544.0x5d8]
[New Thread 7544.0x1d30]
[Thread 7544.0x3a0c exited with code 0]
[Thread 7544.0x2328 exited with code 0]
[Thread 7544.0x1d30 exited with code 0]
[Thread 7544.0x5d8 exited with code 0]
[New Thread 7544.0x46e4]
[New Thread 7544.0x43ec]
[New Thread 7544.0x2594]
[Thread 7544.0x2594 exited with code 1]
[New Thread 7544.0x630]
[Thread 7544.0x630 exited with code 1]
[New Thread 7544.0x399c]
[Thread 7544.0x399c exited with code 1]
[New Thread 7544.0x3f80]
[New Thread 7544.0x4324]
[Thread 7544.0x4324 exited with code 0]
[Thread 7544.0x3f80 exited with code 0]
[Thread 7544.0x43ec exited with code 0]
[Thread 7544.0x46e4 exited with code 0]
[New Thread 7544.0x35fc]
[New Thread 7544.0x256c]
[New Thread 7544.0x2050]
[New Thread 7544.0xc9c]
[Thread 7544.0x256c exited with code 0]
[Thread 7544.0x35fc exited with code 0]
[New Thread 7544.0x3368]
[New Thread 7544.0x4178]
[Thread 7544.0x4178 exited with code 0]
[Thread 7544.0x3368 exited with code 0]
[Thread 7544.0xc9c exited with code 0]
[Thread 7544.0x2050 exited with code 0]
[New Thread 7544.0x32a0]

Thread 44 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 7544.0x32a0]
0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
(gdb) bt
#0  0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007fff84ffcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007fff84947614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007fff84f826a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) q
A debugging session is active.

        Inferior 1 [process 7544] will be detached.

Quit anyway? (y or n) y
Detaching from program: C:\opt\emacs\bin\emacs.exe, process 7544
[Inferior 1 (process 7544) detached]









In GNU Emacs 29.0.60 (build 1, x86_64-w64-mingw32) of 2023-01-02 built
 on DESKTOP-CIHAF12
Windowing system distributor 'Microsoft Corp.', version 10.0.19044
System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.2364)

Configured using:
 'configure --with-native-compilation=aot --without-dbus'

Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS TREE_SITTER WEBP XPM ZLIB

Important settings:
  value of $LANG: CHS
  locale-coding-system: cp936

Major mode: ELisp/l

Minor modes in effect:
  flymake-mode: t
  global-git-commit-mode: t
  magit-auto-revert-mode: t
  auto-revert-mode: t
  shell-dirtrack-mode: t
  server-mode: t
  outline-minor-mode: t
  reveal-mode: t
  save-place-mode: t
  savehist-mode: t
  global-diff-hl-mode: t
  diff-hl-mode: t
  global-dash-fontify-mode: t
  dash-fontify-mode: t
  override-global-mode: t
  auto-compile-on-load-mode: t
  auto-compile-on-save-mode: t
  auto-compile-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  global-prettify-symbols-mode: t
  prettify-symbols-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  temp-buffer-resize-mode: t

Load-path shadows:
c:/Users/Aqua/.config/emacs/lib/transient/lisp/transient hides c:/opt/emacs/share/emacs/29.0.60/lisp/transient
c:/Users/Aqua/.config/emacs/lib/use-package/use-package hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-lint hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-lint
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-jump hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-jump
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-ensure hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-ensure
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-ensure-system-package hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-ensure-system-package
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-diminish hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-diminish
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-delight hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-delight
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-core hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-core
c:/Users/Aqua/.config/emacs/lib/use-package/use-package-bind-key hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/use-package-bind-key
c:/Users/Aqua/.config/emacs/lib/use-package/bind-key hides c:/opt/emacs/share/emacs/29.0.60/lisp/use-package/bind-key

Features:
(shadow sort mail-extr emacsbug face-remap checkdoc flymake-proc flymake
project thingatpt tramp-sh tramp tramp-loaddefs trampver
tramp-integration cus-edit pp cus-start cus-load files-x tramp-compat
parse-time iso8601 man magit-submodule magit-obsolete magit-blame
magit-stash magit-reflog magit-bisect magit-push magit-pull magit-fetch
magit-clone magit-remote magit-commit magit-sequence magit-notes
magit-worktree magit-tag magit-merge magit-branch magit-reset
magit-files magit-refs magit-status magit package browse-url url
url-proxy url-privacy url-expand url-methods url-history url-cookie
url-domsuf url-util url-handlers url-parse auth-source url-vars
magit-repos magit-apply magit-wip magit-log which-func imenu magit-diff
smerge-mode diff git-commit log-edit message sendmail mailcap yank-media
puny rfc822 mml mml-sec password-cache epa derived epg rfc6068
epg-config gnus-util time-date mm-decode mm-bodies mm-encode mail-parse
rfc2231 rfc2047 rfc2045 mm-util ietf-drums mail-prsvr mailabbrev
mail-utils gmm-utils mailheader add-log magit-core magit-autorevert
autorevert filenotify magit-margin magit-transient magit-process
with-editor shell pcomplete magit-mode transient edmacro kmacro
magit-git magit-base magit-section format-spec crm compat-27 dired
dired-loaddefs server epkg-elpa json map epkg-utils epkg-list epkg-desc
find-func epkg emacsql-sqlite-builtin sqlite closql emacsql-sqlite
advice emacsql emacsql-compiler llama compat-26 compile
text-property-search comint ansi-osc ansi-color ring vc-git noutline
outline reveal saveplace savehist recentf tree-widget wid-edit diff-hl
log-view pcvs-util vc-dir ewoc vc vc-dispatcher diff-mode eieio byte-opt
eieio-core dash use-package use-package-ensure use-package-delight
use-package-diminish use-package-bind-key bind-key easy-mmode
use-package-core with-editor-autoloads use-package-autoloads
treepy-autoloads transient-autoloads magit-autoloads llama-autoloads
git-modes-autoloads epkg-autoloads emacsql-autoloads diff-hl-autoloads
dash-autoloads compat-autoloads closql-autoloads borg-autoloads
auto-compile-autoloads borg loaddefs-gen generate-lisp-file lisp-mnt
radix-tree pcase info jka-compr auto-compile comp comp-cstr warnings
icons subr-x rx cl-seq cl-macs gv cl-extra help-mode compat compat-macs
cl-loaddefs cl-lib bytecomp byte-compile china-util rmc iso-transl
tooltip cconv eldoc paren electric uniquify ediff-hook vc-hooks
lisp-float-type elisp-mode mwheel dos-w32 ls-lisp disp-table
term/w32-win w32-win w32-vars term/common-win tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode
prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-bar mouse jit-lock font-lock syntax font-core
term/tty-colors frame minibuffer nadvice seq simple cl-generic
indonesian philippine cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek
romanian slovak czech european ethiopic indian cyrillic chinese
composite emoji-zwj charscript charprop case-table epa-hook
jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button loaddefs
theme-loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget keymap
hashtable-print-readable backquote threads w32notify w32 lcms2 multi-tty
make-network-process native-compile emacs)

Memory information:
((conses 16 296963 51271)
 (symbols 48 22365 4)
 (strings 32 77770 4132)
 (string-bytes 1 2727040)
 (vectors 16 52699)
 (vector-slots 8 1065938 75872)
 (floats 8 124 323)
 (intervals 56 3575 0)
 (buffers 984 20))

-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eason Huang <aqua0210@foxmail.com> writes:

> Hi emacs,
>
> When I editing my ~/.config/emacs/init.el file, Emacs will raise a fatal
> error frequenly when flymake-mode enabled.
>
> With a few hours debug, I found that it's related to flymake-mode and
> Borg( A package manager writed by Jonas Bernoulli).
>
> Borg repos: https://github.com/emacscollective/borg
>
>
> This issue can be fixed by disable flymake-mode or without Borg, just
> use package.el to install packages.
>
> It would be nice if I can use Borg with flymake-mode. I am not sure this
> bug if from Borg or flymake-mode or Emacs itself, so I report it here.
>

I also reported an issue to Borg. See more infomation by the link bellow:
https://github.com/emacscollective/borg/issues/140

I guess the issue is cause by the implementation of UI displaying on
MS-Windows.

JoJoão and Eli, do you have any advice on how to debug with this issue?

Thanks in advance.

-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eason Huang <aqua0210@foxmail.com> writes:

> Eason Huang <aqua0210@foxmail.com> writes:
>
>> Hi emacs,
>>
>> When I editing my ~/.config/emacs/init.el file, Emacs will raise a fatal
>> error frequenly when flymake-mode enabled.
>>
>> With a few hours debug, I found that it's related to flymake-mode and
>> Borg( A package manager writed by Jonas Bernoulli).
>>
>> Borg repos: https://github.com/emacscollective/borg
>>
>>
>> This issue can be fixed by disable flymake-mode or without Borg, just
>> use package.el to install packages.
>>
>> It would be nice if I can use Borg with flymake-mode. I am not sure this
>> bug if from Borg or flymake-mode or Emacs itself, so I report it here.
>>
>
> I also reported an issue to Borg. See more infomation by the link bellow:
> https://github.com/emacscollective/borg/issues/140
>
> I guess the issue is cause by the implementation of UI displaying on
> MS-Windows.
>
> JoJoão and Eli, do you have any advice on how to debug with this issue?
>
> Thanks in advance.


Now I can reproduce the issue with `emacs -Q`. So now I can confirm that
the isse is not related to Borg.

We need to use a larger buffer for reproduce.
for example, I use the flmake.el instead of a simple test file.

Steps to reproduce:

1. Start Emacs 29 with emacs -Q
2. C-c C-f ~/test.el to open a test buffer.
3. Copy all the content of flymake.el to ~/test.el
4. Enable flymake-mode with M-x flymake-mode
5. Try to add some blank lines and then C-x C-s to save buffer
6. Repeat step 5 many times, you will get the fatal error pos up.

See the picture by this link:
https://github.com/emacscollective/borg/issues/140#issuecomment-1399414074

-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> Date: Wed, 04 Jan 2023 22:44:22 +0800
> From: Eason Huang <aqua0210@foxmail.com>
> 
> Thread 44 received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 7544.0x32a0]
> 0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
> (gdb) bt
> #0  0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
> #1  0x00007fff84ffcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
> #2  0x00007fff84947614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
> #3  0x00007fff84f826a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
> #4  0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb) q
> A debugging session is active.

At this point, instead of "q", please type:

  (gdb) thread 1
  (gdb) bt

and post the results here.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Wed, 04 Jan 2023 22:44:22 +0800
>> From: Eason Huang <aqua0210@foxmail.com>
>>
>> Thread 44 received signal SIGTRAP, Trace/breakpoint trap.
>> [Switching to Thread 7544.0x32a0]
>> 0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
>> (gdb) bt
>> #0  0x00007fff84fd0bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x00007fff84ffcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x00007fff84947614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
>> #3  0x00007fff84f826a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
>> #4  0x0000000000000000 in ?? ()
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>> (gdb) q
>> A debugging session is active.
>
> At this point, instead of "q", please type:
>
>   (gdb) thread 1
>   (gdb) bt
>
> and post the results here.
>
>
>
>

Hi Eli,

I tried to debug with GDB again and reproduce the issue and the result
is as bellow:

```
➜ ~  ps -name emacs

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     21    47.24      52.12       7.62   16764   1 emacs

➜ ~  mingw

Aqua@DESKTOP-VIHxxxx MINGW64 ~
$ gdb -p 16764
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 16764
[New Thread 16764.0x20f4]
[New Thread 16764.0x16f4]
[New Thread 16764.0x1a18]
Reading symbols from C:\opt\emacs\bin\emacs.exe...
(gdb) c
Continuing.
[Thread 16764.0x1a18 exited with code 0]
[New Thread 16764.0x5230]
[New Thread 16764.0x1ac4]
[Thread 16764.0x1ac4 exited with code 0]
[Thread 16764.0x5230 exited with code 0]
[New Thread 16764.0x525c]
[New Thread 16764.0x442c]
[Thread 16764.0x442c exited with code 0]
[Thread 16764.0x525c exited with code 0]
[New Thread 16764.0x539c]
[New Thread 16764.0x64]
[Thread 16764.0x64 exited with code 0]
[Thread 16764.0x539c exited with code 0]
[New Thread 16764.0x1aac]
[New Thread 16764.0x5094]
[Thread 16764.0x5094 exited with code 0]
[Thread 16764.0x1aac exited with code 0]
[New Thread 16764.0x46cc]
[New Thread 16764.0x50a8]
[New Thread 16764.0xdb0]
[New Thread 16764.0x1114]
[Thread 16764.0x50a8 exited with code 0]
[Thread 16764.0x46cc exited with code 0]
[Thread 16764.0x1114 exited with code 0]
[Thread 16764.0xdb0 exited with code 0]
[New Thread 16764.0x536c]
[New Thread 16764.0x3f7c]
[New Thread 16764.0x1040]
[New Thread 16764.0x28b0]
[Thread 16764.0x3f7c exited with code 0]
[Thread 16764.0x536c exited with code 0]
[Thread 16764.0x28b0 exited with code 0]
[Thread 16764.0x1040 exited with code 0]
[New Thread 16764.0x2ca4]
[New Thread 16764.0x3f1c]
[New Thread 16764.0x4048]
[New Thread 16764.0x5148]
[Thread 16764.0x5148 exited with code 0]
[Thread 16764.0x4048 exited with code 0]
[Thread 16764.0x3f1c exited with code 0]
[Thread 16764.0x2ca4 exited with code 0]
[New Thread 16764.0x1184]

Thread 25 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 16764.0x1184]
0x00007ffda9a90bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
(gdb) thread 1
[Switching to thread 1 (Thread 16764.0x2de4)]
#0  0x00007ffda790a104 in win32u!NtUserMsgWaitForMultipleObjectsEx () from C:\Windows\System32\win32u.dll
(gdb) bt
#0  0x00007ffda790a104 in win32u!NtUserMsgWaitForMultipleObjectsEx () from C:\Windows\System32\win32u.dll
#1  0x00007ffda91207ee in USER32!MsgWaitForMultipleObjectsEx () from C:\Windows\System32\user32.dll
#2  0x00007ff6123470b0 in sys_select (nfds=<optimized out>, rfds=0x72a17fe960, wfds=0x72a17fe968,
    efds=<optimized out>, timeout=<optimized out>, ignored=0x0) at w32proc.c:2504
#3  0x00007ff6122f6d63 in really_call_select (arg=0x72a17fe6e0) at thread.c:612
#4  0x00007ff6122f778e in flush_stack_call_func (arg=0x72a17fe7c0, func=0x7ff6122f6d00 <really_call_select>)
    at lisp.h:4232
#5  thread_select (func=<optimized out>, max_fds=<optimized out>, rfds=rfds@entry=0x72a17fe960,
    wfds=wfds@entry=0x72a17fe968, efds=<optimized out>, efds@entry=0x0, timeout=<optimized out>,
    timeout@entry=0x72a17fe970, sigmask=<optimized out>, sigmask@entry=0x0) at thread.c:644
#6  0x00007ff6122cf1b4 in wait_reading_process_output (time_limit=<optimized out>, nsecs=<optimized out>,
    read_kbd=<optimized out>, read_kbd@entry=-1, do_display=do_display@entry=true, wait_for_cell=<optimized out>,
    wait_for_cell@entry=0x0, wait_proc=<optimized out>, wait_proc@entry=0x0, just_wait_proc=<optimized out>,
    just_wait_proc@entry=0) at process.c:5693
#7  0x00007ff61211bea5 in sit_for (timeout=timeout@entry=0xb6, reading=reading@entry=true,
    display_option=display_option@entry=1) at dispnew.c:6252
#8  0x00007ff6121f9a75 in read_char (commandflag=<optimized out>, map=<optimized out>, map@entry=0x2044bc40db3,
    prev_event=<optimized out>, used_mouse_menu=<optimized out>, used_mouse_menu@entry=0x72a17ff20b,
    end_time=<optimized out>, end_time@entry=0x0) at keyboard.c:2871
#9  0x00007ff6121fb072 in read_key_sequence (keybuf=keybuf@entry=0x72a17ff390, prompt=prompt@entry=0x0,
    dont_downcase_last=dont_downcase_last@entry=false, can_return_switch_frame=can_return_switch_frame@entry=true,
    fix_current_buffer=fix_current_buffer@entry=true, prevent_redisplay=prevent_redisplay@entry=false)
    at keyboard.c:10073
#10 0x00007ff6121fc69c in command_loop_1 () at keyboard.c:1375
#11 0x00007ff61227580d in internal_condition_case (bfun=bfun@entry=0x7ff6121fc4b0 <command_loop_1>,
    handlers=handlers@entry=0x90, hfun=hfun@entry=0x7ff6121f1520 <cmd_error>) at eval.c:1474
#12 0x00007ff6121e8bde in command_loop_2 (handlers=0x90) at keyboard.c:1124
--Type <RET> for more, q to quit, c to continue without paging--

```

-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> From: Eason Huang <aqua0210@foxmail.com>
> Cc: 60556@debbugs.gnu.org
> Date: Sun, 22 Jan 2023 19:22:23 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > At this point, instead of "q", please type:
> >
> >   (gdb) thread 1
> >   (gdb) bt
> >
> > and post the results here.
> >
> >
> >
> >
> 
> Hi Eli,
> 
> I tried to debug with GDB again and reproduce the issue and the result
> is as bellow:

Thanks.  I guess I shouldn't make any assumptions.  So, one last time:
please reproduce the issue, and type:

  (gdb) thread apply all bt

This should produce a backtrace from all the threads in the Emacs
process.  I'd like to see where did we call the abort function, the
one which pops up the Abort dialog.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eason Huang <aqua0210@foxmail.com>
>> Cc: 60556@debbugs.gnu.org
>> Date: Sun, 22 Jan 2023 19:22:23 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > At this point, instead of "q", please type:
>> >
>> >   (gdb) thread 1
>> >   (gdb) bt
>> >
>> > and post the results here.
>> >
>> >
>> >
>> >
>> 
>> Hi Eli,
>> 
>> I tried to debug with GDB again and reproduce the issue and the result
>> is as bellow:
>
> Thanks.  I guess I shouldn't make any assumptions.  So, one last time:
> please reproduce the issue, and type:
>
>   (gdb) thread apply all bt
>
> This should produce a backtrace from all the threads in the Emacs
> process.  I'd like to see where did we call the abort function, the
> one which pops up the Abort dialog.
>
>
>
>

I tried restart Emacs with `emacs -Q` again, turn on GDB and tried to reproduce
issue, When the Abort dialog pops up, then type:
(gdb) thread apply all bt

The result is as bellow:

➜ ~  ps -name emacs

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     20    31.18      35.30       0.55   14608   1 emacs

➜ ~  mingw

Aqua@DESKTOP-VIHxxxx MINGW64 ~
$ gdb -p 14608
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.

Attaching to process 14608
[New Thread 14608.0x50ec]
[New Thread 14608.0x4338]
[New Thread 14608.0x4e10]
[New Thread 14608.0x4bf8]
[New Thread 14608.0x94c]
Reading symbols from C:\opt\emacs\bin\emacs.exe...
(gdb) c
Continuing.
[Thread 14608.0x94c exited with code 0]
[New Thread 14608.0x1c58]
[New Thread 14608.0x1b48]
[Thread 14608.0x1b48 exited with code 0]
[Thread 14608.0x1c58 exited with code 0]
[New Thread 14608.0x5398]
[New Thread 14608.0x23d4]
[Thread 14608.0x23d4 exited with code 0]
[Thread 14608.0x5398 exited with code 0]
[New Thread 14608.0x4b5c]
[New Thread 14608.0x38c0]
[Thread 14608.0x38c0 exited with code 0]
[Thread 14608.0x4b5c exited with code 0]
[New Thread 14608.0x522c]
[New Thread 14608.0x4208]
[Thread 14608.0x4208 exited with code 0]
[Thread 14608.0x522c exited with code 0]
[New Thread 14608.0x22bc]
[New Thread 14608.0x1838]
[New Thread 14608.0x4908]
[New Thread 14608.0x18a8]
[Thread 14608.0x22bc exited with code 0]
[Thread 14608.0x1838 exited with code 0]
[Thread 14608.0x18a8 exited with code 0]
[Thread 14608.0x4908 exited with code 0]
[New Thread 14608.0x1ac4]
[New Thread 14608.0xdb4]
[Thread 14608.0xdb4 exited with code 0]
[Thread 14608.0x1ac4 exited with code 0]
[New Thread 14608.0x38a8]
[New Thread 14608.0x5d8]
[Thread 14608.0x5d8 exited with code 0]
[Thread 14608.0x38a8 exited with code 0]
[New Thread 14608.0x43c0]
[New Thread 14608.0x6e8]
[New Thread 14608.0x4cec]
[New Thread 14608.0x2dec]
[Thread 14608.0x6e8 exited with code 0]
[Thread 14608.0x43c0 exited with code 0]
[Thread 14608.0x2dec exited with code 0]
[Thread 14608.0x4cec exited with code 0]
[New Thread 14608.0x5054]
[New Thread 14608.0x2470]
[Thread 14608.0x2470 exited with code 0]
[Thread 14608.0x5054 exited with code 0]
[New Thread 14608.0x5360]
[New Thread 14608.0x1348]
[Thread 14608.0x1348 exited with code 0]
[Thread 14608.0x5360 exited with code 0]
[New Thread 14608.0x1dec]
[New Thread 14608.0x73c]
[Thread 14608.0x73c exited with code 0]
[Thread 14608.0x1dec exited with code 0]
[New Thread 14608.0x310c]
[New Thread 14608.0x5180]
[Thread 14608.0x5180 exited with code 0]
[Thread 14608.0x310c exited with code 0]
[New Thread 14608.0x1760]
[New Thread 14608.0x4f44]
[Thread 14608.0x4f44 exited with code 0]
[Thread 14608.0x1760 exited with code 0]
[New Thread 14608.0x15f8]
[New Thread 14608.0x4628]
[Thread 14608.0x4628 exited with code 0]
[Thread 14608.0x15f8 exited with code 0]
[New Thread 14608.0x53a4]
[New Thread 14608.0x10c8]
[New Thread 14608.0x4de4]
[New Thread 14608.0x400c]
[Thread 14608.0x400c exited with code 0]
[Thread 14608.0x4de4 exited with code 0]
[Thread 14608.0x10c8 exited with code 0]
[Thread 14608.0x53a4 exited with code 0]
[New Thread 14608.0x3f20]

Thread 43 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 14608.0x3f20]
0x00007ffda9a90bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
(gdb) thread apply all bt

Thread 43 (Thread 14608.0x3f20):
#0  0x00007ffda9a90bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffda9abcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 5 (Thread 14608.0x4bf8):
#0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 14608.0x4e10):
#0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 14608.0x4338):
#0  0x00007ffda7901104 in win32u!NtUserGetMessage () from C:\Windows\System32\win32u.dll
--Type <RET> for more, q to quit, c to continue without paging--



-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> From: Eason Huang <aqua0210@foxmail.com>
> Cc: 60556@debbugs.gnu.org
> Date: Sun, 22 Jan 2023 20:11:23 +0800
> 
> (gdb) thread apply all bt
> 
> Thread 43 (Thread 14608.0x3f20):
> #0  0x00007ffda9a90bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
> #1  0x00007ffda9abcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
> #4  0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> Thread 5 (Thread 14608.0x4bf8):
> #0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
> #1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
> #4  0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> Thread 4 (Thread 14608.0x4e10):
> #0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
> #1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
> #4  0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> Thread 3 (Thread 14608.0x4338):
> #0  0x00007ffda7901104 in win32u!NtUserGetMessage () from C:\Windows\System32\win32u.dll
> --Type <RET> for more, q to quit, c to continue without paging--

Did you type RET there?  Because there should be more threads (at
least 2 more)...

Thanks.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eason Huang <aqua0210@foxmail.com>
>> Cc: 60556@debbugs.gnu.org
>> Date: Sun, 22 Jan 2023 20:11:23 +0800
>> 
>> (gdb) thread apply all bt
>> 
>> Thread 43 (Thread 14608.0x3f20):
>> #0  0x00007ffda9a90bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x00007ffda9abcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
>> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
>> #4  0x0000000000000000 in ?? ()
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>> 
>> Thread 5 (Thread 14608.0x4bf8):
>> #0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
>> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
>> #4  0x0000000000000000 in ?? ()
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>> 
>> Thread 4 (Thread 14608.0x4e10):
>> #0  0x00007ffda9a90b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x00007ffda9a42e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x00007ffda8fa7614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
>> #3  0x00007ffda9a426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
>> #4  0x0000000000000000 in ?? ()
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>> 
>> Thread 3 (Thread 14608.0x4338):
>> #0  0x00007ffda7901104 in win32u!NtUserGetMessage () from C:\Windows\System32\win32u.dll
>> --Type <RET> for more, q to quit, c to continue without paging--
>
> Did you type RET there?  Because there should be more threads (at
> least 2 more)...
>
> Thanks.
>

Sorry, I didn't type RET to show more infomations.

I tried to reproduce again, and the result is as below:

```
➜ ~  ✗ ps -name emacs

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     20    38.86      43.11       2.38    1036   1 emacs

➜ ~  mingw

MINGW64 ~
$ gdb -p 1036
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.

Attaching to process 1036
[New Thread 1036.0x23c8]
[New Thread 1036.0x1744]
[New Thread 1036.0x33d8]
[New Thread 1036.0x20f0]
[New Thread 1036.0x2aa0]
Reading symbols from C:\opt\emacs\bin\emacs.exe...
(gdb) c
Continuing.
[Thread 1036.0x2aa0 exited with code 0]
[New Thread 1036.0x42b8]
[New Thread 1036.0x166c]
[Thread 1036.0x166c exited with code 0]
[Thread 1036.0x42b8 exited with code 0]
[New Thread 1036.0x5b4]
[New Thread 1036.0x2774]
[New Thread 1036.0x2734]
[New Thread 1036.0x2714]
[Thread 1036.0x2774 exited with code 0]
[Thread 1036.0x5b4 exited with code 0]
[Thread 1036.0x2714 exited with code 0]
[Thread 1036.0x2734 exited with code 0]
[New Thread 1036.0x3c78]
[New Thread 1036.0x3494]
[New Thread 1036.0xe90]
[New Thread 1036.0x5c4]
[Thread 1036.0x5c4 exited with code 0]
[Thread 1036.0xe90 exited with code 0]
[Thread 1036.0x3494 exited with code 0]
[Thread 1036.0x3c78 exited with code 0]
[New Thread 1036.0xe88]

Thread 17 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1036.0xe88]
0x00007ffaa4790bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
(gdb) thread apply all bt

Thread 17 (Thread 1036.0xe88):
#0  0x00007ffaa4790bb1 in ntdll!DbgBreakPoint () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffaa47bcc2e in ntdll!DbgUiRemoteBreakin () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007ffaa3317614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffaa47426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 5 (Thread 1036.0x20f0):
#0  0x00007ffaa4790b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffaa4742e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00007ffaa3317614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffaa47426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 1036.0x33d8):
#0  0x00007ffaa4790b14 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffaa4742e17 in ntdll!TpReleaseCleanupGroupMembers () from C:\Windows\SYSTEM32\ntdll.dll
--Type <RET> for more, q to quit, c to continue without paging--
#2  0x00007ffaa3317614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#3  0x00007ffaa47426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 1036.0x1744):
#0  0x00007ffaa2241104 in win32u!NtUserGetMessage () from C:\Windows\System32\win32u.dll
#1  0x00007ffaa3db1b9e in USER32!GetMessageW () from C:\Windows\System32\user32.dll
#2  0x00007ff691a4c969 in w32_msg_pump (msg_buf=msg_buf@entry=0x4d687ffd40) at w32fns.c:3336
#3  0x00007ff691a4d0db in w32_msg_worker (arg=<optimized out>) at w32fns.c:3574
#4  0x00007ffaa3317614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#5  0x00007ffaa47426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 1036.0x23c8):
#0  0x00007ffaa478d744 in ntdll!ZwDelayExecution () from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00007ffaa1fab16e in SleepEx () from C:\Windows\System32\KernelBase.dll
#2  0x00007ff691a83fa9 in timer_loop (arg=0x7ff69202c580 <real_itimer>) at w32proc.c:476
#3  0x00007ffaa3317614 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
--Type <RET> for more, q to quit, c to continue without paging--
#4  0x00007ffaa47426a1 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#5  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 1036.0x23e0):
#0  0x00007ffaa224a104 in win32u!NtUserMsgWaitForMultipleObjectsEx () from C:\Windows\System32\win32u.dll
#1  0x00007ffaa3db07ee in USER32!MsgWaitForMultipleObjectsEx () from C:\Windows\System32\user32.dll
#2  0x00007ff691a870b0 in sys_select (nfds=<optimized out>, rfds=0x4d667fe4d0, wfds=0x4d667fe4d8, efds=<optimized out>, timeout=<optimized out>, ignored=0x0) at w32proc.c:2504
#3  0x00007ff691a36d63 in really_call_select (arg=0x4d667fe250) at thread.c:612
#4  0x00007ff691a3778e in flush_stack_call_func (arg=0x4d667fe330, func=0x7ff691a36d00 <really_call_select>) at lisp.h:4232
#5  thread_select (func=<optimized out>, max_fds=<optimized out>, rfds=rfds@entry=0x4d667fe4d0, wfds=wfds@entry=0x4d667fe4d8, efds=<optimized out>, efds@entry=0x0, timeout=<optimized out>, timeout@entry=0x4d667fe4e0, sigmask=<optimized out>, sigmask@entry=0x0) at thread.c:644
#6  0x00007ff691a0f1b4 in wait_reading_process_output (time_limit=<optimized out>, nsecs=<optimized out>, read_kbd=<optimized out>, read_kbd@entry=-1, do_display=do_display@entry=true, wait_for_cell=<optimized out>, wait_for_cell@entry=0x0, wait_proc=<optimized out>, wait_proc@entry=0x0, just_wait_proc=<optimized out>, just_wait_proc@entry=0) at process.c:5693
#7  0x00007ff69185bea5 in sit_for (timeout=timeout@entry=0xb6, reading=reading@entry=true, display_option=display_option@entry=1) at dispnew.c:6252
#8  0x00007ff691939a75 in read_char (commandflag=<optimized out>, map=<optimized out>, map@entry=0x1a52d6317b3, prev_event=<optimized out>, used_mouse_menu=<optimized out>,--Type <RET> for more, q to quit, c to continue without paging--
 used_mouse_menu@entry=0x4d667fed7b, end_time=<optimized out>, end_time@entry=0x0) at keyboard.c:2871
#9  0x00007ff69193b072 in read_key_sequence (keybuf=keybuf@entry=0x4d667fef00, prompt=prompt@entry=0x0, dont_downcase_last=dont_downcase_last@entry=false, can_return_switch_frame=can_return_switch_frame@entry=true, fix_current_buffer=fix_current_buffer@entry=true, prevent_redisplay=prevent_redisplay@entry=false) at keyboard.c:10073
#10 0x00007ff69193c69c in command_loop_1 () at keyboard.c:1375
#11 0x00007ff6919b580d in internal_condition_case (bfun=bfun@entry=0x7ff69193c4b0 <command_loop_1>, handlers=handlers@entry=0x90, hfun=hfun@entry=0x7ff691931520 <cmd_error>) at eval.c:1474
#12 0x00007ff691928bde in command_loop_2 (handlers=0x90) at keyboard.c:1124
#13 0x00007ff6919b577b in internal_catch (tag=tag@entry=0x102f0, func=func@entry=0x7ff691928bb0 <command_loop_2>, arg=arg@entry=0x90) at eval.c:1197
#14 0x00007ff691928b6c in command_loop () at keyboard.c:1102
#15 0x00007ff691931077 in recursive_edit_1 () at keyboard.c:711
#16 0x00007ff691931440 in Frecursive_edit () at keyboard.c:794
#17 0x00007ff691ac1f00 in main (argc=<optimized out>, argv=0x1a52a371630) at emacs.c:2529
(gdb) q
A debugging session is active.

        Inferior 1 [process 1036] will be detached.

Quit anyway? (y or n) y
Detaching from program: C:\opt\emacs\bin\emacs.exe, process 1036
[Inferior 1 (process 1036) detached]

```

-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> From: Eason Huang <aqua0210@foxmail.com>
> Cc: 60556@debbugs.gnu.org
> Date: Sun, 22 Jan 2023 21:27:02 +0800
> 
> Sorry, I didn't type RET to show more infomations.
> 
> I tried to reproduce again, and the result is as below:

Thanks.  I think I know the reason for this.  Please try the latest
emacs-29 branch, where I hope I've fixed the root cause of these abort
dialogs.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eason Huang <aqua0210@foxmail.com>
>> Cc: 60556@debbugs.gnu.org
>> Date: Sun, 22 Jan 2023 21:27:02 +0800
>>
>> Sorry, I didn't type RET to show more infomations.
>>
>> I tried to reproduce again, and the result is as below:
>
> Thanks.  I think I know the reason for this.  Please try the latest
> emacs-29 branch, where I hope I've fixed the root cause of these abort
> dialogs.
>

Great!

I build the commit c854ef7a18 of emacs-29 branch, and tried it again.

I can confirm that the issue has been fixed.
Now flymake-mode works well on my init.el, no fatal error message again.


-- 
Eason Huang

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> From: Eason Huang <aqua0210@foxmail.com>
> Cc: 60556@debbugs.gnu.org
> Date: Sun, 22 Jan 2023 22:39:01 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Thanks.  I think I know the reason for this.  Please try the latest
> > emacs-29 branch, where I hope I've fixed the root cause of these abort
> > dialogs.
> >
> 
> Great!
> 
> I build the commit c854ef7a18 of emacs-29 branch, and tried it again.
> 
> I can confirm that the issue has been fixed.
> Now flymake-mode works well on my init.el, no fatal error message again.

Thanks for testing, I'm therefore closing this bug.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[João Távora]

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

> I also reported an issue to Borg. See more infomation by the link bellow:
> https://github.com/emacscollective/borg/issues/140
>
> I guess the issue is cause by the implementation of UI displaying on
> MS-Windows.
>
> JoJoão and Eli, do you have any advice on how to debug with this issue?

From my part, not really.

From what I read in the attached issue, it seems Borg does things
with the load path that interferes with Emacs's ability to invoke
itself as a sub-process.

João

[-- Attachment #2: Type: text/html, Size: 691 bytes --]

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eli Zaretskii]

> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 23 Jan 2023 18:26:14 +0000
> Cc: 60556@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> 
> > I also reported an issue to Borg. See more infomation by the link bellow:
> > https://github.com/emacscollective/borg/issues/140
> >
> > I guess the issue is cause by the implementation of UI displaying on
> > MS-Windows.
> >
> > JoJoão and Eli, do you have any advice on how to debug with this issue?
> 
> >From my part, not really. 
> 
> From what I read in the attached issue, it seems Borg does things
> with the load path that interferes with Emacs's ability to invoke
> itself as a sub-process.

No, it was a real (and quite old) bug in Emacs on MS-Windows: the
behavior when Emacs was killed by its parent process (in particular, a
parent Emacs process) neglected to account for the fact that the
Windows equivalent of a signal handler invoked by the kill message was
run by the OS in a separate thread.

So we are lucky that this bug was reported, because now that
fundamental problem is fixed in Emacs.

bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10

[Eason Huang]

João Távora <joaotavora@gmail.com> writes:

>> I also reported an issue to Borg. See more infomation by the link bellow:
>> https://github.com/emacscollective/borg/issues/140
>>
>> I guess the issue is cause by the implementation of UI displaying on
>> MS-Windows.
>>
>> JoJoão and Eli, do you have any advice on how to debug with this issue?
>
>>From my part, not really.
>
> From what I read in the attached issue, it seems Borg does things
> with the load path that interferes with Emacs's ability to invoke
> itself as a sub-process.
>
> João
>

Hi João,


The fatal error issue has been solved by Eli.

For the load path warning "Your `load-path' seems to contain your
 `.emacs.d' directory", I report a new bug#61014, you can see it by
the link bellow:

https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-01/msg01770.html


And you can reproduce the issue by `emacs -Q`, so it's not related to Borg.

Maybe we can discuss at the thread of bug#61014.

-- 
Eason Huang