[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#71853: 29.4; `kill-compilation` does not kill compilation process on
From: |
Eli Zaretskii |
Subject: |
bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows |
Date: |
Thu, 04 Jul 2024 09:18:26 +0300 |
> 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.
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Tze Chian Kam, 2024/07/01
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Eli Zaretskii, 2024/07/01
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Tze Chian Kam, 2024/07/02
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Eli Zaretskii, 2024/07/02
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Tze Chian Kam, 2024/07/02
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Eli Zaretskii, 2024/07/03
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Tze Chian Kam, 2024/07/04
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows,
Eli Zaretskii <=
- bug#71853: 29.4; `kill-compilation` does not kill compilation process on Windows, Eli Zaretskii, 2024/07/20