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 15:49:42 +0200 [thread overview]
Message-ID: <86a5mu49hl.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB39201FBC54FA830AD2E1D7D4C32C2@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Tue, 19 Mar 2024 22:21:09 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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.
>
> MinGW64 libiconv package has already been installed,
> but MinGW64 iconv package was not.
> Now both of them are installed, and gdb seems to work well with shell-mode.
Great.
So it eventually was related to MSYS programs, and I think we can now
close this bug?
next prev parent reply other threads:[~2024-03-19 13:49 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
2024-03-19 13:21 ` awrhygty
2024-03-19 13:49 ` Eli Zaretskii [this message]
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=86a5mu49hl.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).