From: Nick Roberts Date: Tue, 5 Sep 2006 11:01:45 +0000 (+0000) Subject: *** empty log message *** X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a24e1279d80ccf4923e6f8f6ba03294eda061506;p=thirdparty%2Fbinutils-gdb.git *** empty log message *** --- diff --git a/gdb/PROBLEMS.async b/gdb/PROBLEMS.async index 6b22ebb1cf3..a54d586bd2e 100644 --- a/gdb/PROBLEMS.async +++ b/gdb/PROBLEMS.async @@ -1,7 +1,7 @@ -The test mi-async.exp in gdb.mi works with `runtest gdb.mi/"*.exp"' but not +The test mi-async.exp in gdb.mi works with `runtest gdb.mi/mi-async.exp' but not `make check RUNTESFLAGS=mi-async.exp'. GDB doesn't always stop after `start' has been issued. I have witnessed this sometimes when running -the excutable basics interactively with the start command. I guess this is +the executable basics interactively with the start command. I guess this is due to spurious other events but I don't know what they are. Failures in the gdb.mi testsuite when running asynchronously