gdb.c++/annota2.exp: annotate-quit

[Michael Elizabeth Chastain]

dc> Is anybody else seeing this?
dc> Does anybody currently see it KFAIL?

I'll run it a couple of hundred times in the morning and report back.

dc> Is there any chance that the interpreter patch from yesterday
dc> or today might have fixed this bug?

Yes.  The test case reads a prompt from gdb, sends a ^C to gdb,
and expects gdb to react to it.  I suspect there's a race condition
involving job control so that the incoming ^C races with the
operating system enabling gdb to receive signals (as opposed to
the inferior receiving the signal).  So something that touches
the main prompt/read loop could touch this.

(I admit I'm guessing a lot here).

Michael C