Re: (maybe) Async mode failures on PPC

Luis Machado
2008-07-14T16:32:25Z

Steps to reproduce this failure:

1 - Load the watchpoint.exp test binary into gdb.
2 - start it and next over a few lines.

Results:

(gdb) start
Temporary breakpoint 1 at 0x10000894:
file /home/luis/src/gdb/gdb-head/HEAD/gdb/testsuite/gdb.base/watchpoint.c, line 129.
Starting
program: /home/luis/builds/gdb-head/DFP/gdb/testsuite/gdb.base/watchpoint

Temporary breakpoint 1, main ()
at /home/luis/src/gdb/gdb-head/HEAD/gdb/testsuite/gdb.base/watchpoint.c:129
129 struct1.val = 1;
(gdb) watch ptr1
Hardware watchpoint 2: ptr1
(gdb) n
During symbol reading, incomplete CFI data; unspecified registers (e.g.,
r2) at 0x10000894.
130 struct2.val = 2;
(gdb)
131 ptr1 = &struct1;
(gdb)
Target is executing.
(gdb)
Cannot execute this command while the selected thread is running.
(gdb)
Cannot execute this command while the selected thread is running.
(gdb)
Cannot execute this command while the selected thread is running.
(gdb)

On Mon, 2008-07-14 at 12:44 -0300, Luis Machado wrote:
> Hey guys,
>
> I was giving a shot at the testsuite for PPC and some failures showed
> up, related, apparently, to the async mode.
>
> The pattern is like this, first there's a message informing you that the
> "Target is running" and then no other commands will be accepted due to
> "Cannot execute this command while the selected thread is running.".
>
> Is this something we're still addressing or a new problem? Should we
> modify the testcase so it becomes async-aware?
>
> For example, this piece of the watchpoint.exp testcase
>
> (gdb) PASS: gdb.base/watchpoint.exp: until to ival3 assignment
> until^M
> Target is executing.^M
> (gdb) FAIL: gdb.base/watchpoint.exp: until out of loop
> step^M
> Cannot execute this command while the selected thread is running.^M
>
> Regards,
> Luis