From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27318 invoked by alias); 3 Nov 2008 19:50:23 -0000 Received: (qmail 27255 invoked by uid 22791); 3 Nov 2008 19:50:23 -0000 X-Spam-Check-By: sourceware.org Received: from mx1a.swcp.com (HELO mx1a.swcp.com) (216.184.2.64) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Nov 2008 19:49:38 +0000 Received: from ame7.swcp.com (ame7.swcp.com [216.184.2.70]) by mx1a.swcp.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id mA3JnYuT001369; Mon, 3 Nov 2008 12:49:34 -0700 Received: from swcp.com (nousagi.swcp.com [216.184.2.107] (may be forged)) by ame7.swcp.com (8.14.2/8.13.6) with SMTP id mA3JnVEJ086283; Mon, 3 Nov 2008 12:49:32 -0700 (MST) (envelope-from ebo@sandien.com) Date: Mon, 03 Nov 2008 19:50:00 -0000 To: "Michael Snyder" , "ebo@sandien.com" Subject: Re: using gdb to do embedded unit/regression testing From: "EBo" X-Mailer: TWIG 2.7.7 Message-ID: In-Reply-To: <490F4EAB.206@vmware.com> References: , X-Client-IP: 216.184.15.167 Cc: "gdb@sourceware.org" Reply-To: ebo@sandien.com X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (ame7.swcp.com [216.184.2.128]); Mon, 03 Nov 2008 12:49:32 -0700 (MST) X-Virus-Status: Clean Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00017.txt.bz2 Michael Snyder said: > EBo wrote: > > You should check out src/gcc/testsuite. The gcc testsuites on > embedded targets are all set up to use gdb as an execution engine. Thanks for the pointer. It'll take me awhile to crawl through the testsuites and absorb them... > And you get to use dejagnu as your scripting language (lucky you). The last time I took a serious look at dejagnu, which was YEARS ago, it seemed so incomprehensible that I gave up. I'll take another look into it. Thanks for the pointer. > > ...to malloc?... > > Yeah, we've all run into that. > > Use gdb "echo", rather than print. > > Doesn't help if you have variables, but for simple diagnostics it's ok. That did the trick. Thanks! > > The second issue will be cleaning up and formatting the output from the > > automated unit/regression test suites. For this I will want/need to suppress > > almost all output from gdb, and use the print command above to deal with the > > formatting. If I end up using gdb to help do this type of eXtreme/Agile > > program testing I would like to work with the gdb maintainers to have it > > integrated upstream... > > I think you want dejagnu. Thanks, I'll start digging into it... EBo --