GNU bug report logs - #69795
29.1; cmdproxy.exe exits automatically after executing MSYS2 commands

Previous Next

Full log

Message #52 received at 69795 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: awrhygty <at> outlook.com
Cc: 69795 <at> debbugs.gnu.org
Subject: Re: bug#69795: 29.1; cmdproxy.exe exits automatically after
 executing MSYS2 commands
Date: Mon, 18 Mar 2024 15:05:23 +0200

> From: awrhygty <at> outlook.com
> Cc: 69795 <at> debbugs.gnu.org
> Date: Mon, 18 Mar 2024 10:24:59 +0900
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > So one of these two directories somehow triggers the problem?  Or do
> > you need both on PATH to trigger the problem, and if you only add
> > either one of them, the problem does not happen?
> 
> c:\msys64\usr\bin\ matters. And iconv.exe under it makes the difference.
> In the log below, the process continues after the first call of gdb.exe,
> while iconv.exe does not exist.
> And the process finishes after the second call of gdb.exe,
> while iconv.exe exists.

So what is special with iconv.exe?  What does "iconv --version" say?
Also, what DLLs does it load?  You can find out like this:

  objdump -x c:\msys64\usr\bin\iconv.exe | grep -F "DLL Name:"

And if you invoke iconv.exe from the shell buffer directly, does it
also cause "Process shell finished"?

Previous Next

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