This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: Flush ^running
- From: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- To: "Vladimir Prus" <vladimir at codesourcery dot com>, <gdb-patches at sources dot redhat dot com>
- Date: Mon, 6 Oct 2008 09:48:58 -0400
- Subject: RE: Flush ^running
- References: <200810041901.40210.vladimir@codesourcery.com>
Hi,
I've also run into that problem.
When continuing or stepping over a sleep(), I would only see the
^running and *running
after the sleep() call had finished. Just like you , it only happened
when using
the frontend, although is happened with CLI commands from the frontend
(continue, next).
Your patch fixes this issue.
One less thing to worry about.
Thanks!
Marc
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: Saturday, October 04, 2008 11:02 AM
> To: gdb-patches@sources.redhat.com
> Subject: Flush ^running
>
>
> I've run into a case where gdb would not print ^running in response
> to -exec-continue -- at least not during the time frontend is willing
> to wait for the response. The problem only happened for my when gdb
> is driven by a frontend, not on command line; I don't know
> what frontend
> does differently. I've checked in the below patch to fix this.
>
> - Volodya
>
>