Re: [RFA/c++testsuite] New test for constructor breakpoints

[Daniel Jacobowitz <drow@mvista.com>]

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