This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] gdb.base/callfuncs.exp: make all test names unique
- To: fnasser at redhat dot com, msnyder at cygnus dot com
- Subject: Re: [RFA] gdb.base/callfuncs.exp: make all test names unique
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Wed, 23 May 2001 11:16:43 -0700
- Cc: chastain at cygnus dot com, gdb-patches at sources dot redhat dot com
chastain> ! gdb_test "next" "t_double_values\\(double_val1, double_val2\\);.*" "next 1"
chastain> ! gdb_test "next" "t_structs_c\\(struct_val1\\);.*" "next 2"
snyder> I wonder if it would not be preferable to use "next over t_double_values"
snyder> and "next over t_structs_c".
nasser> Michael (Chastain), please check it in your patch with these changes.
nasser> Thank you very much to help eliminating these ambiguities.
Oops, actually that should be "next to t_double_values" rather than
"next over t_double_values" and so on. It still looks better than
"next" or "next 1".
Works for me, I will use "next to t_double_values" and check it in.
Michael