[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Problem specifying path to Debugger script in Debug Configuration
|
I've tried a similar setup as yours without issues.
The only thing is that I don't use sudo (I don't have root access). So, I
have a script
/home/marc/bin/gdb.sh
!#/bin/bash
gdb $*
and it launches properly.
Maybe the sudo is causing a problem?
Marc
Can anyone shed some light on how PATH is determined by a Debug
launcher?
I found that my launcher error goes away if I put my
gdb_root.sh shell script in /usr/bin, alongside gdb itself. It's seems as if
the native PATH is not respected by the Eclipse debug launcher. In summary,
with gdb_root.sh located in /home/tblack, and /home/tblack is on PATH, and
then I specify "gdb_root.sh" as the Debugger command instead of "gdb", I get a
launcher error. With gdb_root.sh located in /usr/bin, and /usr/bin is on PATH,
and then I specify "gdb_root.sh" as the Debugger command instead of "gdb", I
do not get a launcher error. I have verified my PATH is correct by
successfully running my script "gdb_root" at the command line from some
other location. I have restarted Eclipse and even (gasp) the Linux box.
On Thu, Apr 1, 2010 at 5:52 PM, Dave Korn
<dave.korn.cygwin@xxxxxxxxxxxxxx>
wrote:
On 01/04/2010 21:27, Marc Khouzam wrote:
> You are
right, I couldnt' get a relative path to work.
And I have
run into the same problem when trying to use "target sim" +
"load
<executable>" in a .gdbinit file, I also had to use a full
path. I haven't
debugged it yet (will check later) but wonder if
the gdb process is being
launched from the eclipse executable's
$CWD.
cheers,
DaveK
