RE: Local Variables and MIPS

["Hans Kester" <hans at ellips dot nl>]

Denis Pilat wrote:
> Do you have dejagnu 1.4.4 installed ?
> Do you have "runtest" in your path ?
$ runtest --version
WARNING: Couldn't find the global config file.
Expect version is       5.26
Tcl version is          8.4
Framework version is    1.4.2.x

This seems to be an older version, it came with the Cygwin version I am
using at the moment.

So runtest is in my path but it seems that the insight tree used to have
a dejagnu of itself:
... if [ -f ${srcdir}/../../dejagnu/runtest ]; then echo
${srcdir}/../../dejagnu/runtest; ...

> First you can go into the gdb/testsuite build directory and do "make 
> site.exp" following by
> "runtest --di gdb.mi mi-var-block.exp"
> If that "unitary test" works, then you can tell that your environment
is 
> good.

$ make site.exp
make: `site.exp' is up to date.

$ runtest --di gdb.mi mi-var-block.exp
WARNING: Couldn't find the global config file.
Test Run By Hans on Mon Oct 30 09:18:54 2006
Target is mips-unknown-elf
Host   is i686-pc-cygwin

                === gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using ../../../insight-6.5/gdb/testsuite/config/unix.exp as
tool-and-target-specific interface file.
WARNING: Assuming target board is the local machine (which is probably
wrong).
You may need to set your DEJAGNU environment variable.
Running ../../../insight-6.5/gdb/testsuite/gdb.mi/mi-var-block.exp ...
gdb compile failed,
/usr/local/bin/../lib/gcc/mips-elf/4.1.1/../../../../mips-elf/bin/ld:
warning: cannot find entry symbol _start; defaulting to 0000000000400040
/cygdrive/f/TEMP/cce5LCPe.o: In function `main':
../../../insight-6.5/gdb/testsuite/gdb.mi/var-cmd.c:320: undefined
reference to `exit'
collect2: ld returned 1 exit status
WARNING: Testcase compile failed, so all tests in this file will
automatically fail.

ERROR: Delete all breakpoints in mi_delete_breakpoints (timeout)
ERROR: couldn't load
/gcc/build-insight-mips/gdb/testsuite/gdb.mi/var-cmd into /
gcc/build-insight-mips/gdb/testsuite/../../gdb/gdb (end of file).
FAIL: gdb.mi/mi-var-block.exp: create local variable foo
FAIL: gdb.mi/mi-var-block.exp: delete var foo
FAIL: gdb.mi/mi-var-block.exp: create local variable foo
FAIL: gdb.mi/mi-var-block.exp: update all vars: cb foo changed
FAIL: gdb.mi/mi-var-block.exp: create local variable inner_foo
FAIL: gdb.mi/mi-var-block.exp: create local variable foo2
FAIL: gdb.mi/mi-var-block.exp: update foo: did not change
FAIL: gdb.mi/mi-var-block.exp: delete var inner_foo
FAIL: gdb.mi/mi-var-block.exp: update cb
FAIL: gdb.mi/mi-var-block.exp: delete var foo
FAIL: gdb.mi/mi-var-block.exp: delete var foo2
FAIL: gdb.mi/mi-var-block.exp: delete var cb

                === gdb Summary ===

# of unexpected failures        12
# of expected failures          5
# of unresolved testcases       1
/gcc/build-insight-mips/gdb/testsuite/../../gdb/gdb version  6.5 -nx


I guess I will have to learn how to use dejagnu in a cross compiler
environment and all the options it has.

I only wonder if this will get us closer to the actual problem that the
local variables are not shown on mips. The Insight for all other targets
we use works fine: i686-elf-insight, sh-elf-insight and
x86_64-pc-linux-insight. The mips simulator does not show local
variables either and when I type 'info locals' in the console window
they are printed nicely.

Does anyone have a working local variables window on mips-elf-insight?

Hans