* [Bug 1000716] Error launching GDB to run eCos tests
2009-03-10 9:49 [Bug 1000716] New: Error launching GDB to run eCos tests bugzilla-daemon
@ 2009-03-10 9:53 ` bugzilla-daemon
2009-03-10 9:55 ` bugzilla-daemon
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2009-03-10 9:53 UTC (permalink / raw)
To: ecos-bugs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 1000716] Error launching GDB to run eCos tests
2009-03-10 9:49 [Bug 1000716] New: Error launching GDB to run eCos tests bugzilla-daemon
2009-03-10 9:53 ` [Bug 1000716] " bugzilla-daemon
@ 2009-03-10 9:55 ` bugzilla-daemon
2009-03-10 11:08 ` bugzilla-daemon
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2009-03-10 9:55 UTC (permalink / raw)
To: ecos-bugs
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716
--- Comment #2 from John Dallaway <john@dallaway.org.uk> 2009-03-10 09:54:50 ---
-------- Original Message --------
Subject: Re: Re: File not found when running tests
Date: Tue, 10 Mar 2009 09:28:09 +0000
From: Chris Holgate <chris@zynaptic.com>
I ran configtool under strace on openSUSE 11.0 and have seen similar
behaviour to that reported by Sergei. My PATH environment variable is
set up using the "ecosenv.sh" script which places the path to the ARM
tools at the front - as shown:
PATH=/zynaptic/projects/eCos/beta1/gnutools/arm-eabi/bin:/zynaptic/projects/eCos/beta1/ecos-3.0b1/tools/bin:/home/chris/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin
Tests which run successfully are exec'ed as follows:
execve("/zynaptic/projects/eCos/beta1/gnutools/arm-eabi/bin/arm-eabi-gdb",
["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = 0
Which is what I'd expect to see.
Tests which failed are exec'ed like this:
execve("arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)
execve("/bin/arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)
execve("/usr/bin/arm-eabi-gdb", ["arm-eabi-gdb"..., "-nw"..., "-q"...,
"/zynaptic/projects/eCos/beta1/bu"...], [/* 62 vars */]) = -1 ENOENT (No
such file or directory)
write(2, "exec error - No such file or dir"..., 39) = 39
Not only does this not start with the expected path, but the paths that
are tried do not seem to correspond to my PATH environment variable in
any way - for example I don't have the CWD in my path, but it is the
first place being searched. All very odd.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 1000716] Error launching GDB to run eCos tests
2009-03-10 9:49 [Bug 1000716] New: Error launching GDB to run eCos tests bugzilla-daemon
2009-03-10 9:53 ` [Bug 1000716] " bugzilla-daemon
2009-03-10 9:55 ` bugzilla-daemon
@ 2009-03-10 11:08 ` bugzilla-daemon
2009-03-10 11:54 ` bugzilla-daemon
2009-03-25 8:25 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2009-03-10 11:08 UTC (permalink / raw)
To: ecos-bugs
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716
--- Comment #3 from John Dallaway <john@dallaway.org.uk> 2009-03-10 11:08:49 ---
execve() is called from execvp() which will use a default path of
":/bin:/usr/bin" if there is no PATH variable in the environment. So I suspect
an uninitialised variable somewhere within the eCos Configuration Tool is
triggering a failure to setup the PATH environment variable for the GDB
sub-process on occasion.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1000716] Error launching GDB to run eCos tests
2009-03-10 9:49 [Bug 1000716] New: Error launching GDB to run eCos tests bugzilla-daemon
` (2 preceding siblings ...)
2009-03-10 11:08 ` bugzilla-daemon
@ 2009-03-10 11:54 ` bugzilla-daemon
2009-03-25 8:25 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2009-03-10 11:54 UTC (permalink / raw)
To: ecos-bugs
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716
--- Comment #4 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2009-03-10 11:54:49 ---
(In reply to comment #3)
> execve() is called from execvp() which will use a default path of
> ":/bin:/usr/bin" if there is no PATH variable in the environment. So I suspect
> an uninitialised variable somewhere within the eCos Configuration Tool is
> triggering a failure to setup the PATH environment variable for the GDB
> sub-process on occasion.
>
It's pity that I away from my target I would try 'env PATH=${PATH} configtool'
then. I forget to make a mention that I ran 'configtool' under gnome-terminal
session.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 1000716] Error launching GDB to run eCos tests
2009-03-10 9:49 [Bug 1000716] New: Error launching GDB to run eCos tests bugzilla-daemon
` (3 preceding siblings ...)
2009-03-10 11:54 ` bugzilla-daemon
@ 2009-03-25 8:25 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2009-03-25 8:25 UTC (permalink / raw)
To: ecos-bugs
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000716
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag| |Blocking_3.0-
--- Comment #5 from John Dallaway <john@dallaway.org.uk> 2009-03-25 08:25:16 ---
I have been unable to reproduce this issue to date and can see no obvious
problem in the configtool sources.
A workaround to the problem would be to specify the full path to GDB in the
"Inferior" field of the platform description via the Tools->Platforms... menu
item.
Marking as non-blocking for eCos 3.0.
--
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.
^ permalink raw reply [flat|nested] 6+ messages in thread