From: Nick Roberts <nickrob@snap.net.nz>
Date: Tue, 5 Sep 2006 10:10:58 +0000 (+0000)
Subject: Update.
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=fe6bba7f1d54ed91e5ba225788e68a517e149010;p=thirdparty%2Fbinutils-gdb.git

Update.
---

diff --git a/gdb/PROBLEMS.async b/gdb/PROBLEMS.async
index 1fb9468e6b1..6b22ebb1cf3 100644
--- a/gdb/PROBLEMS.async
+++ b/gdb/PROBLEMS.async
@@ -1,13 +1,16 @@
-1) You can't exit at the end with CTRL-D, the process has to be killed. Typing
-"q" just makes it hang.
+The test mi-async.exp in gdb.mi works with `runtest gdb.mi/"*.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
+due to spurious other events but I don't know what they are.
 
-2) The inferior can't accept input (on the same terminal):
+Failures in the gdb.mi testsuite when running asynchronously
+(set GDBFLAGS "-nw --async" in site.exp) are sometimes due to switching
+thread e.g.
 
--exec-run
-^running
-(gdb)
-Enter value for n1 : 5
-Enter value for n2 :
-Suspended (tty input)
-
-This also happens with Apple's GDB but I don't understand it.
+~"[Switching to process 7738]\n"
+*stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",
+                                                      ^^^
+frame={addr="0x0804839a",func="callee4",args=[],file="../.././gdb/testsuite/gdb.mi/basics.c",fullname="/home/nickrob/src1/gdb/testsuite/gdb.mi/basics.c",line="30"}
+(gdb) 
+FAIL: gdb.mi/mi2-stack.exp: next in callee4 (timeout)