gdb.threads/manythreads.exp: can't read "test": no such variable
authorPedro Alves <palves@redhat.com>
Tue, 31 Mar 2015 17:36:51 +0000 (18:36 +0100)
committerPedro Alves <palves@redhat.com>
Wed, 1 Apr 2015 14:30:13 +0000 (15:30 +0100)
If interrupt_and_wait manages to trigger the FAIL path, we get:

  ERROR OCCURED: can't read "test": no such variable

gdb/testsuite/ChangeLog:
2015-04-01  Pedro Alves  <palves@redhat.com>

* gdb.threads/manythreads.exp (interrupt_and_wait): Pass $message
to fail instead of non-existent $test.

gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/manythreads.exp

index 9fb8307acdca27ff0c9ee23e1520313e670c75ef..dfce0c0fc5d1c883d1238f384d382b71e7d3710e 100644 (file)
@@ -1,3 +1,8 @@
+2015-04-01  Pedro Alves  <palves@redhat.com>
+
+       * gdb.threads/manythreads.exp (interrupt_and_wait): Pass $message
+       to fail instead of non-existent $test.
+
 2015-04-01  Pedro Alves  <palves@redhat.com>
 
        * lib/gdb.exp (gdb_spawn_with_cmdline_opts): Append space to
index b031f68ff74cdb8f54ea90c0f7d3e5b39bf2a597..2a55f868a01983c45c65a4b999378c3ec818ec12 100644 (file)
@@ -95,7 +95,7 @@ proc interrupt_and_wait { message } {
            #  foo () at foo.c:31
            #  31      bar ();
            #
-           fail $test
+           fail $message
        }
     }
 }
This page took 0.046581 seconds and 4 git commands to generate.