[Bug remote/30774] New: GDB fails to parse command passed to be run via pipe on Windows

[Bug remote/30774] New: GDB fails to parse command passed to be run via pipe on Windows

[valeros08 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

            Bug ID: 30774
           Summary: GDB fails to parse command passed to be run via pipe
                    on Windows
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: valeros08 at gmail dot com
  Target Milestone: ---

Hi there!

I've encountered an strange issue in GDB v12.1 when attempting to connect to a
remote target using a pipe on Windows. The command that is supposed to launch a
debug server is not being parsed at all. 

Steps to reproduce:
-------------------
1. Install GDB v12 on the target system. I tried these ones:
https://github.com/ssbssa/gdb/releases/tag/gdb-12.1.90.20220502
https://github.com/espressif/binutils-gdb/releases/tag/esp-gdb-v12.1_20221002

2. Open a new command prompt
3. Enter the following command to initiate a remote target connection via pipe:
```
gdb -ex "target extended-remote | Path\\to\\any\\dummy\\gdb_server.exe --arg1
--arg2"
```

Observed Behavior:
------------------
GDB does not parse the command correctly, the command is simply passed without
any processing, resulting in a failure to start a remote connection. Instead,
an error message is displayed indicating that the command was not parsed at all
(even "|" was not removed).
```
error starting child process '| gdb_server.exe --arg1 --arg2': CreateProcess:
No such file or directory
```

Expected Behavior:
------------------
GDB should parse the provided command correctly and establish a remote target
connection via the specified pipe command.

Additional Information:
-----------------------

- The issue persists across multiple attempts and on different systems where
GDB v12 is installed.
- The previous and the newer versions of GDB (e.g. v11 and v13) do not exhibit
this parsing issue and can establish a remote target connection via the same
pipe command without any problems.

Please let me know if any further information is needed to investigate and
resolve this issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
                 CC|                            |tromey at sourceware dot org
   Last reconfirmed|                            |2023-08-18
     Ever confirmed|0                           |1

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
IIUC, this fails for GDB 12 and works for GDB 13?

If that's correct, then I'm afraid we're just going to close this,
because the GDB 12 branch is closed -- there won't be any more
releases from that branch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows

[valeros08 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

--- Comment #2 from Valerii Koval <valeros08 at gmail dot com> ---
(In reply to Tom Tromey from comment #1)
> IIUC, this fails for GDB 12 and works for GDB 13?
> 
> If that's correct, then I'm afraid we're just going to close this,
> because the GDB 12 branch is closed -- there won't be any more
> releases from that branch.

That's true, the issue is only reproducible with GDB 12. Although it's sad to
hear that there won't be any bug fix releases in the v12 branch as there are
plenty of projects like ESP-IDF that uses GDB 12 as their main package.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED
   Target Milestone|---                         |13.1

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Valerii Koval from comment #2)

> That's true, the issue is only reproducible with GDB 12. Although it's sad
> to hear that there won't be any bug fix releases in the v12 branch as there
> are plenty of projects like ESP-IDF that uses GDB 12 as their main package.

Yeah, I understand.  And, as a project, gdb is sometimes amenable
to backports of fixes to release branches, even in cases like this
where the branch is closed.  However, that requires someone to
dig up the patch, backport it, show it is harmless and/or doesn't
depend on other patches, etc...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug remote/30774] GDB fails to parse command passed to be run via pipe on Windows

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30774

--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
I haven't tried to backport/test it, but the problem description matches this
commit:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=c43d829bca5e45c5e6c0255a549abc5766f6de7f

-- 
You are receiving this mail because:
You are on the CC list for the bug.