unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "xhcoding@163.com" <xhcoding@163.com>
Cc: 52414@debbugs.gnu.org
Subject: bug#52414: backtrace when emacs get to stuck
Date: Sat, 11 Dec 2021 17:26:42 +0200	[thread overview]
Message-ID: <8335mzqi19.fsf@gnu.org> (raw)
In-Reply-To: <202112112135185068261@163.com> (xhcoding@163.com)

> Date: Sat, 11 Dec 2021 21:35:19 +0800
> From: "xhcoding@163.com" <xhcoding@163.com>
> 
> main thread bt:
> 
> #0  0x00007ffc20370764 in ntdll!ZwWaitForAlertByThreadId ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> (gdb) bt
> #0  0x00007ffc20370764 in ntdll!ZwWaitForAlertByThreadId ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #1  0x00007ffc2033379d in ntdll!RtlWaitOnAddress ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #2  0x00007ffc20333652 in ntdll!RtlWaitOnAddress ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #3  0x00007ffc2033346d in ntdll!RtlWaitOnAddress ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #4  0x00007ffc202ffcb4 in ntdll!RtlEnterCriticalSection ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #5  0x00007ffc202ffae2 in ntdll!RtlEnterCriticalSection ()
>    from C:\Windows\SYSTEM32\ntdll.dll
> #6  0x00007ffc1f7ac6ad in msvcrt!_setmode ()
>    from C:\Windows\System32\msvcrt.dll
> #7  0x00007ffc1f7aaccd in msvcrt!_close () from C:\Windows\System32\msvcrt.dll
> #8  0x00007ff7e7bfac26 in sys_close (fd=5) at w32.c:8613
> #9  0x00007ff7e7a868ea in posix_close (fd=5, flag=1) at sysdep.c:2439
> #10 0x00007ff7e7a86928 in emacs_close (fd=5) at sysdep.c:2457
> #11 0x00007ff7e7b741b5 in close_process_fd (fd_addr=0x1cc84de9e24)
>     at process.c:2040

Thanks.  We are trying to close a handle on which the reader thread
already started reading, so the OS doesn't let us delete it.

This whole pipe-process stuff is flaky on MS-Windows.  Patches to fix
it are welcome.





  reply	other threads:[~2021-12-11 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 13:06 bug#52414: 29.0.50; delete the process created by make-pipe-process will cause xhcoding
2021-12-11 12:57 ` Eli Zaretskii
2021-12-11 13:35 ` bug#52414: backtrace when emacs get to stuck xhcoding
2021-12-11 15:26   ` Eli Zaretskii [this message]
2021-12-11 18:18     ` Eli Zaretskii
     [not found]       ` <202112120931422260143@163.com>
2021-12-12  6:52         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8335mzqi19.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52414@debbugs.gnu.org \
    --cc=xhcoding@163.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).