unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: awrhygty@outlook.com
Cc: 69795@debbugs.gnu.org
Subject: bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
Date: Tue, 19 Mar 2024 14:32:16 +0200	[thread overview]
Message-ID: <86edc64d2n.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB392052555B8C890285FC5396C32D2@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)

> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Tue, 19 Mar 2024 07:54:51 +0900
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> 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?
> 
> Here is the log, and the process finished automatically.
> 
> c:\tmp>c:\msys64\usr\bin\iconv.exe --version
> c:\msys64\usr\bin\iconv.exe --version
> iconv (GNU libiconv 1.17)
> Copyright (C) 2000-2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Written by Bruno Haible.
> 
> c:\tmp>
> Process shell finished
> 
> > Also, what DLLs does it load?  You can find out like this:
> >
> >   objdump -x c:\msys64\usr\bin\iconv.exe | grep -F "DLL Name:"
> 
> I have no objdump. I hope output of ldd.exe helps.
> 
> c:\tmp>c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
> c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
> 	ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffd19ad0000)
> 	KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffd17c60000)
> 	KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffd172f0000)
> 	msys-iconv-2.dll => /usr/bin/msys-iconv-2.dll (0x5603f0000)
> 	msys-intl-8.dll => /usr/bin/msys-intl-8.dll (0x430b30000)
> 	msys-2.0.dll => /usr/bin/msys-2.0.dll (0x180040000)
> 
> c:\tmp>
> Process shell finished
> 
> 
> /usr/bin/ is same as c:\msys64\usr\bin\.

So you have an MSYS build of iconv.exe, and it seems to be causing
these problems.  You don't have a MinGW64 build of iconv.exe (in the
c:\msys64\mingw64\bin\ directory).  So if GD|B needs to invoke
iconv.exe, it will invoke the MSYS build, as it cannot find any other
one.  So my suggestion is to download the MinGW64 build of iconv.exe
and install it in the c:\msys64\mingw64\bin\ directory.  It is
supposed to be part of the libiconv package, I think this is it:

  https://packages.msys2.org/package/mingw-w64-x86_64-libiconv

Please tell if doing that solves the problem.





  reply	other threads:[~2024-03-19 12:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 10:55 bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands awrhygty
2024-03-14 11:25 ` Eli Zaretskii
2024-03-14 15:56   ` awrhygty
2024-03-14 16:48     ` Eli Zaretskii
2024-03-15 12:10       ` awrhygty
2024-03-15 12:49         ` Eli Zaretskii
2024-03-16  3:52           ` awrhygty
2024-03-16  8:21             ` Eli Zaretskii
2024-03-16 13:14               ` awrhygty
2024-03-16 17:34                 ` Eli Zaretskii
2024-03-17  1:06                   ` awrhygty
2024-03-17  6:18                     ` Eli Zaretskii
2024-03-17 16:12                       ` awrhygty
2024-03-17 16:24                         ` Eli Zaretskii
2024-03-18  1:24                           ` awrhygty
2024-03-18 13:05                             ` Eli Zaretskii
2024-03-18 22:54                               ` awrhygty
2024-03-19 12:32                                 ` Eli Zaretskii [this message]
2024-03-19 13:21                                   ` awrhygty
2024-03-19 13:49                                     ` Eli Zaretskii
2024-03-19 14:26                                       ` awrhygty
2024-03-19 15: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=86edc64d2n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69795@debbugs.gnu.org \
    --cc=awrhygty@outlook.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 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).