stack walk fail: current thread changes after break

Bug type: Debugger

Describe the bug

• OS and Version: ubuntu 18.04
• VS Code Version: 1.61.2
• C/C++ Extension Version: 1.7.1
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is : The current thread changes right after break causing the command stack-list-frames to fail.

To Reproduce
Embedded linux kernel debugging

1: (49668) ->*stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame={addr="0xffffff80037a3390",func="kvx_eth_get_ethtool_stats",args=[{name="netdev",value="0xffffff804a0f0000"},{name="stats",value="0xffffff80495afbe8"},{name="data",value="0xffffff90400d5000"}],file="<path>",fullname="<path>",line="116",arch="kvx:kv3-1:64"},thread-id="10",stopped-threads=["10"]
116	{
1: (49668) <-1035-stack-list-frames 0 1000
1: (49668) ->1035^error,msg="Selected thread is running."
1: (49668) ->(gdb)
1: (49669) 1035: elapsed time 0
1: (49669) Stack walk failed on thread: 10
1: (49670) Send Event AD7MessageEvent
ERROR: Error while trying to enter break state. Debugging will now stop. Failed to find thread 10 for break event
1: (49671) <--gdb-exit

Riproducete il caso di debug del kernel Linux embedded descritto nell’issue, concentrandovi sull’evento di arresto del breakpoint, sul comando stack-list-frames e sull’errore di cambio thread segnalato. Tracciate la gestione del debugger per il thread 10 e verificate che lo stack walking abbia esito positivo dopo un breakpoint senza segnalare il thread selezionato come in esecuzione.