This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI: "^running" issues
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Vladimir Prus <ghost at cs dot msu dot su>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 5 Sep 2007 17:23:48 +1200
- Subject: Re: MI: "^running" issues
- References: <200709041653.22357.ghost@cs.msu.su>
> I've just run into a somewhat nasty behaviour of gdb.
> Suppose if you've set 5 hardware watchpoints (on x86)
> and to -exec-step. The output from gdb will be:
>
> (gdb) -exec-next
> ^running
> (gdb)
> 34^error,msg="...."
I can't reproduce this. It looks like partial recipe.
>...
> - Killing the idea of async commands. It does not seem to be very useful
> at this point, so we might be better off ripping it and implementing afresh
> later, when it's understood what they should be.
I'm working in the opposite direction: trying to get GDB to work asynchronously.
I don't see the point of ripping out what is already there.
--
Nick http://www.inet.net.nz/~nickrob