[Bug 1000716] Error launching GDB to run eCos tests

[bugzilla-daemon at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716


John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergei.gavrikov@gmail.com




--- Comment #1 from John Dallaway <john@dallaway.org.uk>  2009-03-10 09:53:00 ---
-------- Original Message --------
Subject: Re: Re: File not found when running tests
Date: Mon, 9 Mar 2009 22:18:33 +0200
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>

My guesswork aboud libstdc++ was wrong. I am/was sure that all arm gnu
tools in my PATH, but 'arm-eabi-gdb' does not run itself in configtool

21668 execve("arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q",
"/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such
file or directory)
21668 execve("/bin/arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q",
"/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such
file or directory)
21668 execve("/usr/bin/arm-eabi-gdb", ["arm-eabi-gdb", "-nw", "-q",
"/opt/testing/untitled_install/te"...], [/* 40 vars */]) = -1 ENOENT (No such
file or directory)
21668 write(2, "exec error - No such file or dir"..., 39) = 39
...

Why I was sure? I sourced /opt/ecos/ecosenv.sh before to run configtool.
The 'which' found arm-eabi-gdb. I checked it.

... Just for fun I did fulfil

sudo ln -f -s /opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb /usr/bin

then re-run configtool... and the problem went away.

Then I did remove that symlink and reduce my PATH variable to a classic
path

export PATH=/usr/sbin:/usr/bin:/sbin:/bin
. /opt/ecos/ecosenv.sh

echo $PATH
/opt/ecos/gnutools/i386-elf/bin:/opt/ecos/gnutools/arm-eabi/bin:/opt/ecos/ecos-3.0b1/tools/bin:/usr/sbin:/usr/bin:/sbin:/bin

which arm-eabi-gdb
/opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb

which configtool 
/opt/ecos/ecos-3.0b1/tools/bin/configtool

strace -f -o trace /opt/ecos/ecos-3.0b1/tools/bin/configtool

and the tests ran under configtool:

22084 execve("/opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gdb", ["arm-eabi-gdb",
"-nw", "-q", "/opt/testing/untitled_install/te"...], [/* 39 vars */]) = 0
22084 brk(0)                            = 0x8324000

Hmm. Is it possible that my original PATH too long?

/home/sg/bin:/home/sg/ecos/gnutools/arm-eabi/bin:/home/sg/ecos/gnutools/i386-elf/bin:/home/sg/ecos/tools/bin:/opt/TclDevKit-5.0/bin:/opt/ActiveTcl-8.5/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

Once again, I sourced 'ecosenv.sh' before to run 'configtool'. I have no
ecos stuff under /usr/local. The same tools are placed under my
~/ecos/gnutools directory. And I am/was? sure that 'ecosenv.sh'
overwrites it.

My conclusion, configtool _has_no_bug_. IMHO, it should work on the
fresh-installed systems. Now, I wonder, What's about openSuSE?


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.