This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/22907] New: [Regression] gdbserver doesn't work with filename-only binaries
- From: "sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 01 Mar 2018 17:33:46 +0000
- Subject: [Bug gdb/22907] New: [Regression] gdbserver doesn't work with filename-only binaries
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=22907
Bug ID: 22907
Summary: [Regression] gdbserver doesn't work with filename-only
binaries
Product: gdb
Version: 8.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: sergiodj at redhat dot com
Reporter: sergiodj at redhat dot com
CC: brobecker at adacore dot com, simon.marchi at ericsson dot com
Target Milestone: 8.1
Simon Marchi mentioned on IRC that, after the startup-with-shell feature has
been implemented on gdbserver, it is not possible to specify a filename-only
binary, like:
$ gdbserver :1234 a.out
/bin/bash: line 0: exec: a.out: not found
During startup program exited with code 127.
Exiting
This happens on systems where the current directory "." is not listed in the
PATH environment variable. Although including "." in the PATH variable is a
possible workaround, this can be considered a regression because before
startup-with-shell it was possible to use only the filename (due to reason that
gdbserver used "exec*" directly).
--
You are receiving this mail because:
You are on the CC list for the bug.