> Thanks, this is fine with me.  Just a really small nit, I would suggest
> initializing the line_actual variable to 0 or -1 (an invalid line number)
> prior to calling gdb_test_multiple.  This way, if that test fails,
> line_actual will still be defined, and the expression that refers to it will
> generate a FAIL instead of an unreadable tcl backtrace.

Sounds good. Just for kicks, I took at look at what it looks like
when the variable is undefined, and the error message is obvious
about why it fails. When the error is defined, however, you have
to figure out what the difference is, and track the value of that
variable down. What won me over to your suggestion is that the
error can go unnoticed if you just compare .sum files...

Attached is the patch I just pushed (re-tested on x86_64-linux).

-- 
Joel