Re: Dejagnu testsuite

[Manoj Iyer <manjo@austin.ibm.com>]

For example how does the testcase translate variables like $hex? how does
it know that $hex is the right value that GDB prints??

--
Manjo

On Wed, 14 Apr 2004, Manoj Iyer wrote:

>
> ok, go it! I was able to run the testcase, now I am trying to determine
> why the testcase broke/failed, is there a way to re-create the failure
> manually by running GDB against the test (using the assertion) that
> failed?
>
> --
> Manjo
>
> On Wed, 14 Apr 2004, Jason Molenda wrote:
>
> > Hi Manoj,
> >
> > On Apr 14, 2004, at 11:35 AM, Manoj Iyer wrote:
> >
> > > Is there any documentation on how to compile and execute the testsuite
> > > that is part of the GDB package?
> >
> > After you've built gdb, and have tcl, expect, and dejagnu pre-installed
> > on your system or have them in your build tree, you just run "make
> > check-gdb".  Any tests that fail will print a FAIL message to the
> > screen; in gdb/testsuite there are two files of note, "gdb.sum" and
> > "gdb.log".  The former shows the status of each test which ran.  The
> > latter shows all of the communication with gdb during the test run.
> >
> > There are many ways to change how tests are run, etc., this is most
> > easily done with the RUNTESTFLAGS argument to make.  e.g. to run the
> > mi-stack.exp tests only you would do
> >
> > make check-gdb RUNTESTFLAGS=mi-stack.exp
> >
> > You can also pass "--help" as the RUNTESTFLAGS arg and you'll get a
> > list of all the options it will accept.
> >
> > That should get you started.
> >
> > Jason
> >
> >
>