From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-15034-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 8519 invoked by alias); 3 May 2002 22:20:14 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 8435 invoked from network); 3 May 2002 22:20:02 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by sources.redhat.com with SMTP; 3 May 2002 22:20:02 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id g43MJxL15375;
	Fri, 3 May 2002 17:19:59 -0500
Date: Fri, 03 May 2002 15:20:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200205032219.g43MJxL15375@duracef.shout.net>
To: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: RFA: Check for corruption of cv_type chain
Cc: drow@mvista.com
X-SW-Source: 2002-05/txt/msg00082.txt.bz2

! # These tests are intended to catch problems in the STABS reader, so I
! # think it's okay to override the preference the user expressed in
! # their $DEJAGNU file or whatever, and explicitly request extended
! # stabs debugging information.  But, if we don't know how to do that,
! # these tests still should pass just fine if the executable uses some
! # other format.

As Daniel J said, please don't do that.

This makes life harder for me.  I'd like the tests to be agnostic about
the configurations, and then have the test bed software iterate over
all the interesting configurations.

Suppose that a similar bug started happening with -gdwarf-3, or with a
coff version of gcc (such as Cygwin's gcc), or with the native Solaris
or Irix or HP-UX C++ compiler?

Michael C