From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EAEEB3858023; Wed, 6 Oct 2021 19:14:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EAEEB3858023 From: "simon.marchi at polymtl dot ca" To: gdb-prs@sourceware.org Subject: [Bug server/28392] gdb server no longer supports argument globbing and variable substitution Date: Wed, 06 Oct 2021 19:14:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at polymtl dot ca X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2021 19:14:46 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28392 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at polymtl do= t ca --- Comment #4 from Simon Marchi --- I don't really know what's best here. I just tried your different examples= to get a feel of the problem, but I don't have a definite answer. It seems difficult to reconcile all use cases. I think it's good if GDB and GDBserver have the same behavior. It's also g= ood if that behavior is predictable. I think we have to choose the behavior th= at makes the most sense, make sure it works the same in GDB and GDBserver, and stick to it / make sure it is properly tested. Whatever we choose, I think some people will be unhappy (will see a change of behavior in their use cas= e). Disregarding things work today, I think makes sense that when using startup-with-shell, the arguments are passed unchanged to the shell (althou= gh concatenated with spaces if more than one is given). Otherwise, the option= to run through a shell is kind of pointless. --=20 You are receiving this mail because: You are on the CC list for the bug.=