GNU bug report logs - #71853
29.4; `kill-compilation` does not kill compilation process on Windows

Previous Next

Full log

Message #48 received at 71853-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: tze.chian.kam <at> gmail.com
Cc: 71853-done <at> debbugs.gnu.org
Subject: Re: bug#71853: 29.4;
 `kill-compilation` does not kill compilation process on Windows
Date: Sat, 20 Jul 2024 12:50:26 +0300

> Cc: 71853 <at> debbugs.gnu.org
> Date: Thu, 04 Jul 2024 09:18:26 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > From: Tze Chian Kam <tze.chian.kam <at> gmail.com>
> > Date: Thu, 4 Jul 2024 14:30:15 +1000
> > Cc: 71853 <at> 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.

No further comments in two weeks, so I'm now closing this bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.