Breakpoints set in thread does not work in UI

[infn-ke]

If I set a breakpoint in a thread, then UI does not work correctly. I can see the debug console correctly shows that the breakpoint was hit. But UI is completely off from this point and onward. Is there any specific setting needed to be done for UI to work correctly when working on threads?

Running gdbserver 9.1 on 32 bit arm.

[GitMensch]

What do you mean with "UI is completely off"? A screenshot likely helps, a debug log would be useful, too.

[infn-ke]

The UI does not show that the breakpoint is hit (does not open file and manually opening file does not show it either). The little status bar says target is running. I do see this error message;

Failed to get Stack Trace: Selected thread is running. (from stack-list-frames --thread 1 0 7)

as well as this one

Could not get threads: Cannot execute this command while the target is running. Use the "interrupt" command to stop the target and then try again. (from thread-info)

[GitMensch]

What does the gdb console show?

Does it work if you explicit run interrupt on the console?

It seems that either the breakpoint was not hit or the extension issued a re-run - so the full log output will be useful to check that.

[infn-ke]

I was able to re-create the issue once on gdb command line. Will continue to investigate;

(gdb) c
Continuing.
[New Thread 473.473]
../../gdb-9.1/gdb/thread.c:95: internal-error: thread_info* inferior_thread(): Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

[GitMensch]

It may be the case that the thread was not selected when GDB stopped, which would be necessary (or a different thread was selected).

Can you please recheck (with current extension version or preferably the current Git version) and report your findings?