+2004-10-11 Orjan Friberg <orjanf@axis.com>
+
+ * gdb.threads/bp_in_thread.exp: Use runto_main and "continue" instead
+ of "run", since the latter doesn't work with remote targets. Adjust
+ the breakpoint numbering accordingly.
+ * gdb.threads/pthread_cond_wait.exp: Ditto.
+
2004-10-08 Michael Chastain <mec.gnu@mindspring.com>
* gdb.base/overlays.exp: Update copyright years.
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
+runto_main
gdb_test "break noreturn" \
- "Breakpoint 1 at .*: file .*${srcfile}, line .*" \
+ "Breakpoint 2 at .*: file .*${srcfile}, line .*" \
"breakpoint on noreturn"
# Run the program and make sure GDB reports that we stopped after
# hitting breakpoint 1 in noreturn().
-gdb_test "run" \
- ".*Breakpoint 1, noreturn ().*" \
+gdb_test "continue" \
+ ".*Breakpoint 2, noreturn ().*" \
"run to noreturn"
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
+runto_main
gdb_test "break break_me" \
- "Breakpoint 1 at .*: file .*${srcfile}, line .*" \
+ "Breakpoint 2 at .*: file .*${srcfile}, line .*" \
"breakpoint on break_me"
-gdb_test "run" \
- ".*Breakpoint 1, break_me ().*" \
+gdb_test "continue" \
+ ".*Breakpoint 2, break_me ().*" \
"run to break_me"
#