unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tze Chian Kam <tze.chian.kam@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71853@debbugs.gnu.org
Subject: bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows
Date: Thu, 4 Jul 2024 14:30:15 +1000	[thread overview]
Message-ID: <CABodVWWc5xdTixO54GdWL1wLNdwytxAcdEhUvjJRMayXSJ8N3w@mail.gmail.com> (raw)
In-Reply-To: <86h6d6bu8d.fsf@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

> So, bottom line, I see no bug here, only known limitations of handling
> sub-processes on MS-Windows.

Thanks for your help.





  reply	other threads:[~2024-07-04  4:30 UTC|newest]

Thread overview: 14+ 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 [this message]
2024-07-04  6:18                     ` Eli Zaretskii
2024-07-20  9:50                       ` 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=CABodVWWc5xdTixO54GdWL1wLNdwytxAcdEhUvjJRMayXSJ8N3w@mail.gmail.com \
    --to=tze.chian.kam@gmail.com \
    --cc=71853@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).