From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31605 invoked by alias); 21 Sep 2004 17:03:40 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31598 invoked from network); 21 Sep 2004 17:03:39 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 21 Sep 2004 17:03:39 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1C9o3H-0001kk-2H; Tue, 21 Sep 2004 13:03:39 -0400 Date: Tue, 21 Sep 2004 17:03:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: gdb-patches@sources.redhat.com Subject: Re: Testing the Dwarf ICU patches Message-ID: <20040921170338.GA6691@nevyn.them.org> Mail-Followup-To: Jim Blandy , gdb-patches@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-09/txt/msg00346.txt.bz2 On Tue, Sep 21, 2004 at 11:59:41AM -0500, Jim Blandy wrote: > > What's the best way to go about making sure this doesn't break? It > would be nice to have at least one *.exp file that would make GDB > trace a few inter-CU references each time the tests were run. We'd need a way to write dwarf2 by hand for that. Long overdue :-) -- Daniel Jacobowitz