Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Vladimir Prus" <vladimir@codesourcery.com>,
	        <gdb-patches@sources.redhat.com>
Subject: RE: Flush ^running
Date: Mon, 06 Oct 2008 13:49:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA063DBBDF@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <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
> 
> 


      parent reply	other threads:[~2008-10-06 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04 15:02 Vladimir Prus
2008-10-04 18:16 ` Daniel Jacobowitz
2008-10-06 13:49 ` Marc Khouzam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6D19CA8D71C89C43A057926FE0D4ADAA063DBBDF@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox