From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9201 invoked by alias); 14 Apr 2004 20:29:27 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9141 invoked from network); 14 Apr 2004 20:29:25 -0000 Received: from unknown (HELO e35.co.us.ibm.com) (32.97.110.133) by sources.redhat.com with SMTP; 14 Apr 2004 20:29:25 -0000 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i3EKTKnr071690; Wed, 14 Apr 2004 16:29:20 -0400 Received: from austin.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i3EKTJx3285718; Wed, 14 Apr 2004 14:29:20 -0600 Received: from lazy.austin.ibm.com (lazy.austin.ibm.com [9.53.94.97]) by austin.ibm.com (8.12.10/8.12.10) with ESMTP id i3EKTFbt111242; Wed, 14 Apr 2004 15:29:18 -0500 Date: Wed, 14 Apr 2004 20:46:00 -0000 From: Manoj Iyer X-X-Sender: manjo@lazy To: Jason Molenda cc: gdb@sources.redhat.com Subject: Re: Dejagnu testsuite In-Reply-To: <65F7C997-8E45-11D8-8B96-000393D457E2@apple.com> Message-ID: References: <65F7C997-8E45-11D8-8B96-000393D457E2@apple.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-04/txt/msg00082.txt.bz2 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 > >