unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: awrhygty@outlook.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69795@debbugs.gnu.org
Subject: bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
Date: Mon, 18 Mar 2024 01:12:18 +0900	[thread overview]
Message-ID: <TYZPR01MB39200CDA476B7C7F1EBFC9B7C32E2@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <86a5mx5qkc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 17 Mar 2024 02:18:46 -0400")

Eli Zaretskii <eliz@gnu.org> writes:

> Nothing jumps out as an obvious problem, but you did say that setting
> PATH affects this?  How does it affect the problem?  Is there a recipe
> where you invoke GDB with a different PATH, and don't see "Process
> shell finished" after exiting GDB?  If so, can you show a recipe with
> that different PATH?

Simply skipping PATH settings, cmdproxy.exe continues normally after
quitting c:\msys64\mingw64\bin\gdb.exe(full path needed.)

> Btw, why do you add these directories to PATH in the first place?  The
> second one is a directory with MSYS executables, so why do you need it
> for running GDB?  The first one is for MinGW64 executables, but since
> you invoke GDB via n explicit absolute file name, you don't need to
> add the directory to PATH.

If I decide to use MSYS environment generally, those directories are
added to system PATH setting and emacs implicitly refers to the value.
In such case, I will call gdb without directory prefix.
But currently it is problematic and I am likely to search for another
gdb binary.





  reply	other threads:[~2024-03-17 16:12 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 [this message]
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=TYZPR01MB39200CDA476B7C7F1EBFC9B7C32E2@TYZPR01MB3920.apcprd01.prod.exchangelabs.com \
    --to=awrhygty@outlook.com \
    --cc=69795@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).