From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19661 invoked by alias); 20 Feb 2002 00:04:04 -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 19499 invoked from network); 20 Feb 2002 00:04:01 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 20 Feb 2002 00:04:01 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g1K03xl32217; Tue, 19 Feb 2002 18:03:59 -0600 Date: Tue, 19 Feb 2002 16:04:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200202200003.g1K03xl32217@duracef.shout.net> To: drow@mvista.com Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints Cc: gdb-patches@sources.redhat.com X-SW-Source: 2002-02/txt/msg00515.txt.bz2 Aieee, I am having an instant allergic reaction to -notransfer. Nothing else in the test suite uses it except for some internal multi-line stuff in gdb_test which I do not trust at all. So we get to be the first soldier on the beach. I don't want to have result variations depending on what version of "expect" somebody has. There's got to be a better way of tracking which breakpoints have been successfully set. Maybe set_bp_overloaded should record that information? Michael C