GDB now takes 4 minutes to start up with remote gdbserver target
Sandra Loosemore
sandra@codesourcery.com
Fri Jul 24 16:05:00 GMT 2015
On 07/24/2015 04:34 AM, Gary Benson wrote:
> Sandra Loosemore wrote:
>> (4) GDB doesn't respond to ^C during the 4 minutes it is doing
>> whatever it's doing to transfer files. It just sits there acting
>> catatonic.
>
> Sandra, could you tell me if this patch makes GDB interruptible for
> you?
No, it is not doing anything to help. It only notices the ^C when it
finishes whatever it is doing and reaches the breakpoint at main, same
as before.
Also, what kind of state would you expect GDB to be left in, if it could
be interrupted? It might be somewhat reassuring to users to get back to
a gdb prompt so they know it's still alive, but if there's nothing to
indicate what was taking so long and any attempt to continue debugging
the program results in another long delay while the file transfer is
retried, that wouldn't be helpful.
-Sandra
More information about the Gdb
mailing list