diff options
| author | Nick Roberts <nickrob@snap.net.nz> | 2006-09-17 22:58:36 +0000 |
|---|---|---|
| committer | Nick Roberts <nickrob@snap.net.nz> | 2006-09-17 22:58:36 +0000 |
| commit | 4aaf12e8c09b7c5badc70983efa77a18858af260 (patch) | |
| tree | bc5d03825aa1d599d53e2c2bcfc8ef83b884308b | |
| parent | fed17c4b481956f827298e824acabfb63453b45d (diff) | |
| download | fsf-binutils-gdb-4aaf12e8c09b7c5badc70983efa77a18858af260.zip fsf-binutils-gdb-4aaf12e8c09b7c5badc70983efa77a18858af260.tar.gz fsf-binutils-gdb-4aaf12e8c09b7c5badc70983efa77a18858af260.tar.bz2 | |
Update.
| -rw-r--r-- | gdb/PROBLEMS.async | 17 |
1 files changed, 1 insertions, 16 deletions
diff --git a/gdb/PROBLEMS.async b/gdb/PROBLEMS.async index a54d586..4bb1213 100644 --- a/gdb/PROBLEMS.async +++ b/gdb/PROBLEMS.async @@ -1,16 +1 @@ -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 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 -(set GDBFLAGS "-nw --async" in site.exp) are sometimes due to switching -thread e.g. - -~"[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) +1) Can't debug multi-threaded programs asynchronously (linux_nat_wait). |