On 05/17/2013 03:51 AM, Pedro Alves wrote:
> As long as we're revising... :-)

Sure!

> set tst "complete on \"filesy\""
> send_gdb "break filesy\t"
> gdb_test_multiple "" $tst {
>      -re "^break filesy\\\x07m" {
> 	pass $tst
>
> 	# Now ask for the completion list
> 	set tst "completion list for \"filesym\""
> 	send_gdb "\t\t"
> 	gdb_test_multiple "" $tst {
> 	    -re "\\\x07\r\nfilesym\[ \t\]+filesym.c\[ \t\]+\r\n$gdb_prompt " {
> 		pass $tst
>
> 		# Flush the rest of the output by creating the breakpoint.
> 		# This ensures this file passes testsuite/12649.
> 		send_gdb "\n"
> 		gdb_test "" "Breakpoint 1.*" "set breakpoint at filesym"
> 	    }
> 	}
>      }
> }

I've used this verbatim and tested with the read1 scenario, too. All 
looks good.

Keith

ChangeLog

2013-05-20  Keith Seitz  <keiths@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.base/filesym.exp: Use gdb_test_multiple instead of
	gdb_expect.
	Add test to flush the remaining input buffer so that this
	file passes testsuite/12649.