From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-12868-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 7814 invoked by alias); 18 Feb 2002 20:26:03 -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 7696 invoked from network); 18 Feb 2002 20:25:53 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by sources.redhat.com with SMTP; 18 Feb 2002 20:25:53 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id g1IKPpc04061;
	Mon, 18 Feb 2002 14:25:51 -0600
Date: Mon, 18 Feb 2002 12:26:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200202182025.g1IKPpc04061@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/msg00483.txt.bz2

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:

  gcc 3.0.3, -gdwarf-2
  gcc 3.0.3, -gstabs+
  gcc 3.0.4-20020215, -gdwarf-2
  gcc 3.0.4-20020215, -gstabs+
  gcc gcc-3_0-branch, -gdwarf-2
  gcc gcc-3_0-branch, -gstabs+
  gcc HEAD, -gdwarf-2
  gcc HEAD, -gstabs+

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.

Michael C

===

2002-02-14  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.c++/ovldbreak.exp: Test breakpoints on the constructors.