RE: Local Variables and MIPS

RE: Local Variables and MIPS

[Hans Kester]

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

Re: Local Variables and MIPS

[Denis PILAT]

Hans Kester wrote:
> $ 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.
>   
Well I didn't catch you were working under cygwin.
What I can tell you is that for Linux hosts you need to use 1.4.4 
framework since gdb6.3 version.
I'm not using cygwin for my validation.
> 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; ...
>
>   
The makefile first tries to check if you got the dejagnu source package 
next to the gdb distribution, in that case it will use this one.

Local Variables and MIPS

[Hans Kester]

I seem to have this issue: http://sourceware.org/ml/insight/2004-q1/msg00033.html
When I type "info locals" it prints the local variables, the tool tips are also working properly, but my Local Variables window is empty. Does anyone have an idea? I am using the 'real' Insight 6.5.

Hans Kester
 

Re: Local Variables and MIPS

[Keith Seitz]

Hans Kester wrote:
> I seem to have this issue: http://sourceware.org/ml/insight/2004-q1/msg00033.html
> When I type "info locals" it prints the local variables, the tool tips are also working properly, but my Local Variables window is empty. Does anyone have an idea? I am using the 'real' Insight 6.5.

Have you tried any of the things suggested in the post (running testsuite)?

Is it reproducible using a simulator?

Keith

RE: Local Variables and MIPS

[Hans Kester]

I will try the testsuite when I have more time. The simulator has the
same behaviour.

Regards,

Hans Kester
 

-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com] 
Sent: Thursday, October 19, 2006 5:43 PM
To: Hans Kester
Cc: insight@sourceware.org
Subject: Re: Local Variables and MIPS

Hans Kester wrote:
> I seem to have this issue:
http://sourceware.org/ml/insight/2004-q1/msg00033.html
> When I type "info locals" it prints the local variables, the tool tips
are also working properly, but my Local Variables window is empty. Does
anyone have an idea? I am using the 'real' Insight 6.5.

Have you tried any of the things suggested in the post (running
testsuite)?

Is it reproducible using a simulator?

Keith

RE: Local Variables and MIPS

[Hans Kester]

The testsuite shows this:

$ make RUNTESTFLAGS="mi-var-block.exp mi-var-display.exp
mi-var-child.exp mi-var-cmd.exp" check
make[1]: Entering directory `/gcc/build-insight-mips'
make[2]: Entering directory `/gcc/build-insight-mips/bfd'
Making check in doc
make[3]: Entering directory `/gcc/build-insight-mips/bfd/doc'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/gcc/build-insight-mips/bfd/doc'
Making check in po
make[3]: Entering directory `/gcc/build-insight-mips/bfd/po'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/gcc/build-insight-mips/bfd/po'
make[3]: Entering directory `/gcc/build-insight-mips/bfd'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/gcc/build-insight-mips/bfd'
make[2]: Leaving directory `/gcc/build-insight-mips/bfd'
make[2]: Entering directory `/gcc/build-insight-mips/opcodes'
Making check in po
make[3]: Entering directory `/gcc/build-insight-mips/opcodes/po'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/gcc/build-insight-mips/opcodes/po'
make[3]: Entering directory `/gcc/build-insight-mips/opcodes'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/gcc/build-insight-mips/opcodes'
make[2]: Leaving directory `/gcc/build-insight-mips/opcodes'
make[2]: Entering directory `/gcc/build-insight-mips/etc'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/gcc/build-insight-mips/etc'
make[2]: Entering directory `/gcc/build-insight-mips/tcl'
cd win && make tcltest
make[3]: Entering directory `/gcc/build-insight-mips/tcl/win'
make[3]: Nothing to be done for `tcltest'.
make[3]: Leaving directory `/gcc/build-insight-mips/tcl/win'
rootme=`pwd`; export rootme; \
srcdir=../../insight-6.5/tcl; export srcdir ; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then  \
   TCL_LIBRARY=`cd ${srcdir}/library && pwd` ; \
   export TCL_LIBRARY ; fi ; \
runtest mi-var-block.exp mi-var-display.exp mi-var-child.exp
mi-var-cmd.exp --to
ol tcl --srcdir ../../insight-6.5/tcl/testsuite
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
Test Run By Hans on Thu Oct 26 17:25:20 2006
Native configuration is i686-pc-cygwin

                === tcl tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for targe
t.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using ../../insight-6.5/tcl/testsuite/config/default.exp as
tool-and-target-spec
ific interface file.

                === tcl Summary ===

Tcl library is version

make[2]: Leaving directory `/gcc/build-insight-mips/tcl'
make[2]: Entering directory `/gcc/build-insight-mips/itcl'
for dir in itcl itk iwidgets ; do \
        if test -d $dir ; then \
            echo "$dir: make check" ;\
            if (cd $dir; make check) ; then true ; else exit 1 ; fi ; \
        else \
            exit 1; \
        fi \
done;
itcl: make check
make[3]: Entering directory `/gcc/build-insight-mips/itcl/itcl'
make[3]: *** No rule to make target `check'.  Stop.
make[3]: Leaving directory `/gcc/build-insight-mips/itcl/itcl'
make[2]: *** [check] Error 1
make[2]: Leaving directory `/gcc/build-insight-mips/itcl'
make[1]: *** [check-itcl] Error 2
make[1]: Leaving directory `/gcc/build-insight-mips'
make: *** [do-check] Error 2

Re: Local Variables and MIPS

[Keith Seitz]

Hans Kester wrote:
> The testsuite shows this:
> 
> $ make RUNTESTFLAGS="mi-var-block.exp mi-var-display.exp
> mi-var-child.exp mi-var-cmd.exp" check
> make[1]: Entering directory `/gcc/build-insight-mips'
> make[2]: Entering directory `/gcc/build-insight-mips/bfd'
                                                        ^^^

It would be a lot easier if you did this from 
/gcc/build-insight-mips/gdb/testsuite.

Keith

RE: Local Variables and MIPS

[Hans Kester]

Keith,

Point taken... I guess I am just one of those happy users of Insight who
don't know too much about the internals and have never run any testsuite
before. Here is what I get now:

$ make RUNTESTFLAGS="mi-var-block.exp mi-var-display.exp
mi-var-child.exp mi-var-cmd.exp" check
Nothing to be done for all...
rootme=`pwd`; export rootme; \
srcdir=../../../insight-6.5/gdb/testsuite ; export srcdir ; \
EXPECT=`if [ -f ${rootme}/../../expect/expect ] ; then echo
${rootme}/../../expect/expect ; else echo expect ; fi` ; export EXPECT ;
\
EXEEXT=.exe ; export EXEEXT ; \
 
LD_LIBRARY_PATH=$rootme/../../expect:$rootme/../../libstdc++:$rootme/../
../tk/unix:$rootme/../../tcl/unix:$rootme/../../bfd:$rootme/../../opcode
s:$LD_LIBRARY_PATH; \
export LD_LIBRARY_PATH; \
if [ -f ${rootme}/../../expect/expect ] ; then  \
  TCL_LIBRARY=${srcdir}/../../tcl/library ; \
  export TCL_LIBRARY ; fi ; \
` if [ -f ${srcdir}/../../dejagnu/runtest ]; then echo
${srcdir}/../../dejagnu/runtest; else if [ "i686-pc-cygwin" =
"mips-unknown-elf" ]; then echo runtest; else t='s,^,mips-elf-,; '; echo
runtest | sed -e '' $t; fi; fi` mi-var-block.exp mi-var-display.exp
mi-var-child.exp mi-var-cmd.exp
sed: can't read s,^,mips-elf-,;: No such file or directory
/bin/sh: mi-var-block.exp: command not found
make: *** [just-check] Error 127


Do I need dejagnu somewhere or am I doing something silly again?

Hans