gnucobol-debug icon indicating copy to clipboard operation
gnucobol-debug copied to clipboard

Remote target doesn't support qGetTIBAddr packet

Open GitMensch opened this issue 3 years ago • 1 comments

I've tried a complete new setup, after struggling with the auto-calls of cobc and missing error messages when not explicit set to verbose mode again, I've reached a state where everything should work - but the extension does not attach successful (to be specific: it auto-disconnects. I see the connection in the gdbserver, then "Remote side has terminated connection").

The debug output has the source mapping first, then a lot of GDB output, ending with:

GDB -> App: {"outOfBandRecord":[],"resultRecords":{"resultClass":"error","results":[["msg","Remote target doesn't support qGetTIBAddr packet"]]}}
Remote target doesn't support qGetTIBAddr packet
getThreads
stdin: 9-thread-info
stdout: 9^done,threads=[]
(gdb) 
GDB -> App: {"token":9,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["threads",[]]]}}
stdin: 10-target-detach
stdout: 10^error,msg="The program is not being run."
(gdb) 

GitMensch avatar Sep 23 '21 21:09 GitMensch

Hi @GitMensch, have you ever solved / root-caused this issue? I also get it now when using Native- with remote qemu. The weird thing is, that it worked yesterday and for some reason it stopped working. Already checked a million of things in the past hours. It works to start when I remove the bin/debug executable/file, but then I dont have my breakpoints anymore. So somehow the executable seems to trigger this issue.

jbreu avatar Jun 02 '24 13:06 jbreu