Re: [PATCH] Fix for GDB failing to interrupt after run when no PID issued by stub

Yao Qi
2018-01-31T16:41:52Z

Omair Javaid <omair.javaid@linaro.org> writes:

> Here are the steps to reproduce:
> 1) arm-none-eabi-gdb file-to-debug.elf
> 2) target remote :3333

"target extended-remote :3333".

> At this stage gdb would have connected and halted successfully.
> 3) run
> Issue ctrl + C to interrupt running program and GDB wont be able to stop.

Could you show the log of "set debug remote 1", especially after
"ctrl-c" is typed. I want to understand what is going on over these
packets between GDB and stub, and reproduce it on GDBserver by disabling
some packets. This is what I get,

(gdb) c
Continuing.
Sending packet: $Z0,7ffff7dea940,1#e0...Packet received: OK
Sending packet: $QPassSignals:#f3...Packet received: OK
Sending packet: $Hc0#db...Packet received: OK
Sending packet: $s#73...Packet received: T0506:c0dcffffff7f0000;07:c0dcffffff7f0000;10:7f05400000000000;
Sending packet: $Z0,40057a,1#74...Packet received: OK
Sending packet: $QPassSignals:e;10;14;17;1a;1b;1c;21;24;25;2c;4c;97;#0a...Packet received: OK
Sending packet: $Hcpa410.0#6f...Packet received: E01
Sending packet: $c#63...^Cremote_pass_ctrlc called
remote_interrupt called
Packet received: T0206:ffffffff00000000;07:d8daffffff7f0000;10:e05dadf7ff7f0000;
Sending packet: $qL1200000000000000000#50...Packet received:

Program received signal SIGINT, Interrupt.
Sending packet: $z0,40057a,1#94...Packet received: OK

In the stop reply from my gdbserver, there is no "thread id" either. My
stop reply has expedite registers while OpenOCD doesn't. I don't think
this matters here.

--
Yao (齐尧)