From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10461 invoked by alias); 18 Feb 2002 21:17:31 -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 10320 invoked from network); 18 Feb 2002 21:17:14 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 18 Feb 2002 21:17:14 -0000 Received: from drow by nevyn.them.org with local (Exim 3.34 #1 (Debian)) id 16cv9t-0004Mi-00; Mon, 18 Feb 2002 16:17:13 -0500 Date: Mon, 18 Feb 2002 13:17:00 -0000 From: Daniel Jacobowitz To: Michael Elizabeth Chastain Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints Message-ID: <20020218161713.A16761@nevyn.them.org> Mail-Followup-To: Michael Elizabeth Chastain , gdb-patches@sources.redhat.com References: <200202182025.g1IKPpc04061@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202182025.g1IKPpc04061@duracef.shout.net> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-02/txt/msg00484.txt.bz2 On Mon, Feb 18, 2002 at 02:25:51PM -0600, Michael Elizabeth Chastain wrote: > This patch is returned for rework. I like the patch, but there is > a cascade problem: > > "set_bp_overloaded foo::foo" tests FAIL > the breakpoints are not present > continue_to_bp_constructor issues "continue" unconditionally > the script loses synchronization with the program-under-test at this point > all the tests after that FAIL > > This happens on target=native host=i686-pc-linux-gnu with all the gcc v3 > configurations: This is all over the GDB testsuite. It's a tremendously complicated problem :) > Can you do something in continue_to_bp_constructor to keep synchronization? > Maybe: > > send_gdb "info b ${bpnumber}\n" > gdb_expect { > -re "Num.*\r\n${bpnumber}.*\r\n.*$gdb_prompt $" { > send_gdb "continue\n" > gdb_expect { > ... > } > } > -re "No breakpoint or watchpoint number ${bpnumber}.*gdb_prompt $" { > fail "continue to bp overloaded constructor : ${argtypes}" > } > -re ".*$gdb_prompt $" { > fail "continue to bp overloaded constructor : ${argtypes}" > } > timeout { > fail "continue to bp overloaded constructor : ${argtypes} (timeout)" > } > } > > Or if you have a better idea, go for it. I just want to fix the problem > where all the currently-working tests FAIL if the new tests FAIL. I don't think that would work... let me think about it tonight. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer