[Bug threads/22925] gdb assumes target can activate threads at will, causes internal error in infrun.c in 'finish_step_over'

[Bug threads/22925] gdb assumes target can activate threads at will, causes internal error in infrun.c in 'finish_step_over'

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22925

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I'm a little confused on this one.

On the one hand -- the remote protocol doesn't have a way for
a target to explain that it isn't in control of scheduling.
This could be added, but only with some cooperation from gdb as well.

However in the example you did:

(gdb) b
(gdb) c

Doesn't that "b" set a breakpoint?
Then "continue" has to step off the breakpoint.
This is done by single-stepping, I suppose because
setting another breakpoint is difficult -- gdb or gdbserver
would have to decode instructions to find the next instruction.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug threads/22925] gdb assumes target can activate threads at will, causes internal error in infrun.c in 'finish_step_over'

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22925

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
I think this is a dup.
The other bug mentions RISC-V, but if you read through it all
(it's had a lot of comments, some patches, and been closed and
reopened multiple times), in the end you'll see that the
underlying issues have to do with OpenOCD and stepping generically.

*** This bug has been marked as a duplicate of bug 26819 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.