This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI: "^running" issues
On Wednesday 05 September 2007 09:23:48 Nick Roberts wrote:
> > 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.
I suppose I can try to make a full recipe -- but only if you're intending to fix that ;-)
> >...
> > - 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.
Then, can you please provide a specification of what "asynchronously" means, and
why it's good for users and frontends?
Thanks,
Volodya