On Mon, Mar 29, 2004 at 01:06:07PM -0500, Jeff Johnston wrote:
+send_gdb "continue\n"
+gdb_expect {
Everywhere you're using gdb_expect, please use gdb_test_multiple
instead. For the "after" tests, you can use gdb_test_multiple with
"" as the first argument.
I tried this initially but I kept getting "Error: internal buffer is full".
I tried lowering the "after" time which is why it ended up 100 below but
that didn't solve the problem. Any suggestions on how to avoid the
"full_buffer" error.
I'm not sure about the regexes, since I'm just pulling this out of the
top of my head, but you want something like this:
-re "error:.*$gdb_prompt $" {
fail "msg"
}
-re "\\\[New thread \[^\]\]*\\\]\r\n" {
exp_continue
}
-re "\\\[Thread \[^\]\]* exited\\\]\r\n" {
exp_continue
}
That will consume any thread create/delete messages, instead of leaving
them in the buffer.