gdb testsuite

gdb testsuite

[M R Swami Reddy]

Hello,

I have ported gdb simulator to a 16bit target (ie cr16-elf) and its working with 
all standard test suites (like nullstone, perennial etc).

Now I want to run the gdb test suite using the "make check", but its not 
successful. Could you please let me know, what to do to run the gdb test suite 
completely. Thanks in advance.

Thanks,
Swami

Re: gdb testsuite

[Jim Blandy]

On Jan 25, 2008 2:13 AM, M R Swami Reddy <MR.Swami.Reddy@nsc.com> wrote:
> I have ported gdb simulator to a 16bit target (ie cr16-elf) and its working with
> all standard test suites (like nullstone, perennial etc).
>
> Now I want to run the gdb test suite using the "make check", but its not
> successful. Could you please let me know, what to do to run the gdb test suite
> completely. Thanks in advance.

Will you be contributing this simulator to the public GDB sources?

Re: gdb testsuite

[M R Swami Reddy]

Jim Blandy wrote:
> On Jan 25, 2008 2:13 AM, M R Swami Reddy <MR.Swami.Reddy@nsc.com> wrote:
>> I have ported gdb simulator to a 16bit target (ie cr16-elf) and its working with
>> all standard test suites (like nullstone, perennial etc).
>>
>> Now I want to run the gdb test suite using the "make check", but its not
>> successful. Could you please let me know, what to do to run the gdb test suite
>> completely. Thanks in advance.
> 
> Will you be contributing this simulator to the public GDB sources?

Yes.

Thanks,
Swami

Re: gdb testsuite

[Jim Blandy]

On Jan 27, 2008 9:06 PM, M R Swami Reddy <MR.Swami.Reddy@nsc.com> wrote:
> >> Now I want to run the gdb test suite using the "make check", but its not
> >> successful. Could you please let me know, what to do to run the gdb test suite
> >> completely. Thanks in advance.

One should be able to run programs on the simulator by starting GDB on
the program to be run, typing "target sim", and then "run".  Does this
work?

When you type 'make check-gdb' at the top of your build tree, or 'make
check' in the gdb/testsuite directory of the build tree, what is the
output?  Does it create a gdb.log file?  What are its contents?

Re: gdb testsuite

[M R Swami Reddy]

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Hi Jim,

Thank you very much for your response.

> One should be able to run programs on the simulator by starting GDB on
> the program to be run, typing "target sim", and then "run".  Does this
> work?

I am able to set the target as "sim", load the program and run it on
cr16 gdb simulator (ie cr16-elf-gdb). And I am able to execute a few
C standard test suites using this cr16-elf-gdb tool.

> When you type 'make check-gdb' at the top of your build tree, or 'make
> check' in the gdb/testsuite directory of the build tree, what is the
> output?  Does it create a gdb.log file?  What are its contents?

I did ran the "make check-gdb", but the below results displayed:

=========
                 === gdb Summary ===

# of expected passes            162
# of unexpected failures        343
# of unresolved testcases       18
# of untested testcases         1
# of unsupported tests          12
==========

Please find the gdb.log as an attachment (file name: gdb.log.bz2).

Thanks,
Swami

[-- Attachment #2: gdb.log.bz2 --]
[-- Type: application/octet-stream, Size: 9610 bytes --]

Re: gdb testsuite

[Jim Blandy]

In gdb.log, I see the below.  Note that the test suite tries to run
the program with a direct "run" command, with no 'target sim'.  I
think you need to write an appropriate DejaGnu configuration file for
your target.  I believe there are existing files included with DejaGnu
that might be appropriate for you to model yours on, with names ending
in "-sim", or something like that.

Running ../../../gdb-6.6/gdb/testsuite/gdb.base/a2-run.exp ...
Executing on host: cr16-elf-gcc
../../../gdb-6.6/gdb/testsuite/gdb.base/run.c  -g  -lm   -o
/scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run    (timeout =
300)
GNU gdb 6.6-1.0 20080109 (cr16-elf)

Copyright (C) 2006 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB.  Type "show warranty" for details.

This GDB was configured as "--host=i686-pc-linux-gnu --target=cr16-elf".

(gdb) set height 0

(gdb) set width 0

(gdb) dir

Reinitialize source path to empty? (y or n) y

Source directories searched: $cdir:$cwd

(gdb) dir ../../../gdb-6.6/gdb/testsuite/gdb.base

Source directories searched:
/scratch/user/swami/gdb/build/gdb/testsuite/../../../gdb-6.6/gdb/testsuite/gdb.base:$cdir:$cwd

(gdb) kill

The program is not being run.

(gdb) file /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run

Reading symbols from
/scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run...done.

(gdb) run

Starting program: /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run

Don't know how to run.  Try "help target".

(gdb) FAIL: gdb.base/a2-run.exp: run "run" with no args

Re: gdb testsuite

[M R Swami Reddy]

Hi Jim,

Thank you very much for the analysis.

I have fixed the issue. Now I can see a few more tests passed under gdb:
===
                 === gdb Summary ===

# of expected passes            260
# of unexpected failures        356
# of untested testcases         2
# of unsupported tests          12
/scratch/user/swami/gdb/build/gdb/testsuite/../../gdb/gdb version  6.6-1.0 -nx
====

Created the cr16 target specific simulator tests and able to run these tests.

Thank you very much for your response.

Btw, a compiler option "-lm" passed for all tests. Can I remove the "-lm" option 
during the compilation? Please advise.


Thanks,
Swami


Jim Blandy wrote:
> In gdb.log, I see the below.  Note that the test suite tries to run
> the program with a direct "run" command, with no 'target sim'.  I
> think you need to write an appropriate DejaGnu configuration file for
> your target.  I believe there are existing files included with DejaGnu
> that might be appropriate for you to model yours on, with names ending
> in "-sim", or something like that.
> 
> Running ../../../gdb-6.6/gdb/testsuite/gdb.base/a2-run.exp ...
> Executing on host: cr16-elf-gcc
> ../../../gdb-6.6/gdb/testsuite/gdb.base/run.c  -g  -lm   -o
> /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run    (timeout =
> 300)
> GNU gdb 6.6-1.0 20080109 (cr16-elf)
> 
> Copyright (C) 2006 Free Software Foundation, Inc.
> 
> GDB is free software, covered by the GNU General Public License, and you are
> 
> welcome to change it and/or distribute copies of it under certain conditions.
> 
> Type "show copying" to see the conditions.
> 
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> 
> This GDB was configured as "--host=i686-pc-linux-gnu --target=cr16-elf".
> 
> (gdb) set height 0
> 
> (gdb) set width 0
> 
> (gdb) dir
> 
> Reinitialize source path to empty? (y or n) y
> 
> Source directories searched: $cdir:$cwd
> 
> (gdb) dir ../../../gdb-6.6/gdb/testsuite/gdb.base
> 
> Source directories searched:
> /scratch/user/swami/gdb/build/gdb/testsuite/../../../gdb-6.6/gdb/testsuite/gdb.base:$cdir:$cwd
> 
> (gdb) kill
> 
> The program is not being run.
> 
> (gdb) file /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run
> 
> Reading symbols from
> /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run...done.
> 
> (gdb) run
> 
> Starting program: /scratch/user/swami/gdb/build/gdb/testsuite/gdb.base/run
> 
> Don't know how to run.  Try "help target".
> 
> (gdb) FAIL: gdb.base/a2-run.exp: run "run" with no args
> 

Re: gdb testsuite

[Jim Blandy]

It's not obvious to me where the -lm comes from.  gdb/testsuite/lib
contains a number of files that are also involved in running the
tests; in particular, gdb_compile is defined in
gdb/testsuite/lib/gdb.exp.

One unfortunate characteristic of the GDB test suite is that, even if
GDB is horribly broken, many tests will still pass.  You can't have
much confidence that things are basically working with 356 failures.
You should look through gdb.log and work through a bunch of them to
get a feel for the state of things.

If you're going to do any significant amount of work with the test
suite, I would recommend investing a little time in learning the Tcl
language.  It's built on some very simple concepts, and knowing how
those actually work, instead of guessing based on the resemblance
between Tcl and more familiar languages, will save confusion in the
future.  I think there are tutorials on-line somewhere.

Re: gdb testsuite

[Thiago Jung Bauermann]

On Wed, 2008-01-30 at 09:56 -0800, Jim Blandy wrote:
> One unfortunate characteristic of the GDB test suite is that, even if
> GDB is horribly broken, many tests will still pass.  You can't have
> much confidence that things are basically working with 356 failures.
> You should look through gdb.log and work through a bunch of them to
> get a feel for the state of things.

It's good to be aware of that. Do you mind if I put this paragraph in

http://sourceware.org/gdb/wiki/Testing_GDB ?
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb testsuite

[Jim Blandy]

Be my guest!

On Jan 30, 2008 11:52 AM, Thiago Jung Bauermann <bauerman@br.ibm.com> wrote:
> On Wed, 2008-01-30 at 09:56 -0800, Jim Blandy wrote:
> > One unfortunate characteristic of the GDB test suite is that, even if
> > GDB is horribly broken, many tests will still pass.  You can't have
> > much confidence that things are basically working with 356 failures.
> > You should look through gdb.log and work through a bunch of them to
> > get a feel for the state of things.
>
> It's good to be aware of that. Do you mind if I put this paragraph in
>
> http://sourceware.org/gdb/wiki/Testing_GDB ?
> --
> []'s
> Thiago Jung Bauermann
> Software Engineer
> IBM Linux Technology Center
>
>

Re: gdb testsuite

[Thiago Jung Bauermann]

On Wed, 2008-01-30 at 15:53 -0800, Jim Blandy wrote:
> On Jan 30, 2008 11:52 AM, Thiago Jung Bauermann <bauerman@br.ibm.com> wrote:
> > On Wed, 2008-01-30 at 09:56 -0800, Jim Blandy wrote:
> > > One unfortunate characteristic of the GDB test suite is that, even if
> > > GDB is horribly broken, many tests will still pass.  You can't have
> > > much confidence that things are basically working with 356 failures.
> > > You should look through gdb.log and work through a bunch of them to
> > > get a feel for the state of things.
> >
> > It's good to be aware of that. Do you mind if I put this paragraph in
> >
> > http://sourceware.org/gdb/wiki/Testing_GDB ?
> 
> Be my guest!

Thanks, it's there now.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb testsuite

[M R Swami Reddy]

Hi Jim,

Thanks a bundle for your kind response.

> It's not obvious to me where the -lm comes from.  gdb/testsuite/lib
> contains a number of files that are also involved in running the
> tests; in particular, gdb_compile is defined in
> gdb/testsuite/lib/gdb.exp.

OK. I will explore the 'lib' directory.

> One unfortunate characteristic of the GDB test suite is that, even if
> GDB is horribly broken, many tests will still pass.  You can't have
> much confidence that things are basically working with 356 failures.
> You should look through gdb.log and work through a bunch of them to
> get a feel for the state of things.

Thats true. Yes, iam going through the gdb.log file and analyzing the
failures further.

> If you're going to do any significant amount of work with the test
> suite, I would recommend investing a little time in learning the Tcl
> language.  It's built on some very simple concepts, and knowing how
> those actually work, instead of guessing based on the resemblance
> between Tcl and more familiar languages, will save confusion in the
> future.  I think there are tutorials on-line somewhere.

OK. I will look into the Tcl language.

Thanks,
Swami

gdb testsuite

[qinwei]

hi all,

Any one could tell me if the testsuite now is enough for GDB-6.5, or if 
there are other testsuites for it? 
Thanks!

GDB testsuite

[Rajesh Maddali]

Hi

	I downloaded the test suite for gdb 4.18.
	After running configure on sparc/solaris 2.7, if I run
	"make" it is saying "Nothing to do for all.. "

	Can someone tell me how to build and run testsuite

Thanks
Rajesh
From ac131313@cygnus.com Thu May 20 18:30:00 1999
From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@sourceware.cygnus.com
Subject: FRAMELESS_FUNCTION_INVOCATION and PUSH_ARGUMENTS
Date: Thu, 20 May 1999 18:30:00 -0000
Message-id: <3744B53D.A9B7B1FC@cygnus.com>
X-SW-Source: 1999-q2/msg00103.html
Content-length: 274

Just FYI,

Previously these macro's had side-effects (setting variable
parameters).  I'm cleaning them up so that the side-effects are removed
and a target can implement each macro using a true function.

This change will appear in the next snap.

	enjoy,
		Andrew
From brendan@dgs.monash.edu.au Thu May 20 18:54:00 1999
From: Brendan Simon <brendan@dgs.monash.edu.au>
To: egcs mailing list <egcs@cygnus.com>, gdb <gdb@sourceware.cygnus.com>
Subject: One GCC for all targets.
Date: Thu, 20 May 1999 18:54:00 -0000
Message-id: <3744BB2C.F5FF3F9D@dgs.monash.edu.au>
X-SW-Source: 1999-q2/msg00104.html
Content-length: 447

On the GDB mailing list there was discussion of one GDB executable which
could debug multiple target architectures (eg. PPC, m68k, etc).  I was
wondering if GCC would go down the same track ?  I'm sure that there
would be alot of communication between the GDB and GCC/EGCS people (but
I might be assuming too much).  Does anyone know or have any comments
about future releases of GCC compiling for multiple target
architectures.

Brendan Simon.