From: Eli Zaretskii <eliz@gnu.org>
To: Tze Chian Kam <tze.chian.kam@gmail.com>
Cc: 71853@debbugs.gnu.org
Subject: bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows
Date: Thu, 04 Jul 2024 09:18:26 +0300 [thread overview]
Message-ID: <86bk3dade5.fsf@gnu.org> (raw)
In-Reply-To: <CABodVWWc5xdTixO54GdWL1wLNdwytxAcdEhUvjJRMayXSJ8N3w@mail.gmail.com> (message from Tze Chian Kam on Thu, 4 Jul 2024 14:30:15 +1000)
> From: Tze Chian Kam <tze.chian.kam@gmail.com>
> Date: Thu, 4 Jul 2024 14:30:15 +1000
> Cc: 71853@debbugs.gnu.org
>
> > From: Eli Zaretskii
> > Date: Wed, 03 Jul 2024 14:17:06 +0300
> >
> > I guess our detection of MSYS applications needs some update? Can you
> > show the list of DLLs that your MSYS2 python.exe depends on? If you
> > have GNU Binutils installed, the following command should show that:
> >
> > objdump -x /path/to/python.exe | fgrep "DLL Name"
>
> libpython3.11.dll
> KERNEL32.dll
> msvcrt.dll
If this is the MSYS2 Python, the one you cannot interrupt, I guess
some recent change in Python for Windows causes this problem. Because
my Python is older and I don't have this problem.
prev parent reply other threads:[~2024-07-04 6:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 2:57 bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows Tze Chian Kam
2024-06-30 9:07 ` Eli Zaretskii
[not found] ` <CABodVWXdfXUhjhJNb13hcndALq+7A+L8VBODod7vBbD77DW5Vg@mail.gmail.com>
2024-06-30 17:53 ` Eli Zaretskii
2024-07-01 2:53 ` Tze Chian Kam
2024-07-01 11:27 ` Eli Zaretskii
2024-07-02 6:26 ` Tze Chian Kam
2024-07-02 6:36 ` Tze Chian Kam
2024-07-02 12:43 ` Eli Zaretskii
2024-07-02 12:41 ` Eli Zaretskii
2024-07-03 3:26 ` Tze Chian Kam
2024-07-03 11:17 ` Eli Zaretskii
2024-07-04 4:30 ` Tze Chian Kam
2024-07-04 6:18 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bk3dade5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71853@debbugs.gnu.org \
--cc=tze.chian.kam@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.