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: Sat, 16 Mar 2024 10:21:14 +0200 [thread overview]
Message-ID: <86il1m7fk5.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB392055F8CD86A26FF69336E0C32F2@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Sat, 16 Mar 2024 12:52:19 +0900
>
> > So let's start from the beginning: can you show a recipe, starting
> > from "emacs -Q", where you invoke GDB from Emacs, and cmdproxy (or
> > some other sub-process) exits?
>
> I found that setting PATH make the difference.
> Start emacs -Q, type 'M-x shell RET',
> and input following command lines.
> set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
> c:\msys64\mingw64\bin\gdb.exe
> q
> Then cmdproxy.exe exits automatically.
Please show the value of PATH after "set PATH" above. Like this:
c:\tmp>set PATH
(I have a very different MinGW directory tree here, but I tried to do
something equivalent to what you do above, and couldn't reproduce it:
I get placed at the cmd.exe prompt, as expected.)
And once again: it is not cmdproxy that exits, it's cmd.exe. cmdproxy
will not exit until the process it started, in this case cmd.exe,
exits.
Btw, why do you end each element of PATH with a backslash '\' ? This
is not required. (I don't think it's part of your problem, but
still.)
next prev parent reply other threads:[~2024-03-16 8:21 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 [this message]
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
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=86il1m7fk5.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).