This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re[2]: (a?)synchronous stepping commands in gdb MI, a week later
- From: Konstantin Karganov <kostik at ispras dot ru>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 29 Nov 2004 20:52:45 +0300
- Subject: Re[2]: (a?)synchronous stepping commands in gdb MI, a week later
- Organization: ISP RAS
- References: <3616850089.20041129165854@ispras.ru> <41AB43C8.7050500@gnu.org>
- Reply-to: Konstantin Karganov <kostik at ispras dot ru>
Hello Andrew,
>> Does anyone know why the "-exec-*" commands family in GDB MI is
>> declared asynchronous but in fact behaves synchronously (blocking the
>> interface until the execution completes)?
> Asynchronous behavior depends on an asynchronous backend. At present
> only ``target async-remote'' is asynchronous (and then there's doubt
> that it still works), hence the behavior you're seeing.
So it's just obsolete documentation, that states asynchronous
behavior? Or there are plans to add asynchronous commands later?
One more question: when the execution of "next" (or "step") command in
GDB is interrupted is there a way to know where it would stop if not
interrupted?
Or, maybe, the way to continue the execution of interrupted GDB command
as if there was no interrupt?..
Thanks a lot.
--
Best regards,
Konstantin