Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [commit/obish] Fix cntrl-z
Date: Wed, 12 Feb 2003 18:42:00 -0000	[thread overview]
Message-ID: <20030212184232.GA30842@nevyn.them.org> (raw)
In-Reply-To: <ro1y94lflm2.fsf@jackfruit.Stanford.EDU>

On Wed, Feb 12, 2003 at 09:35:17AM -0800, David Carlton wrote:
> On Wed, 12 Feb 2003 16:36:28 +0100, Andrew Cagney <ac131313@redhat.com> said:
> 
> > The attatched gets rid of the immediate problem of cntrl-z not
> > working.  When async, it calls cli_command_loop.  Thanks to mark for
> > analyzing the problem.
> 
> This patch (or some other patch since yesterday and today) causes
> gdb.c++/annota2.exp: annotate-quit (PR gdb/544) to start KFAILing
> again for me.  (It had been passing since the interpreter stuff
> finished merging in a week or two ago.)
> 
> An old, harmless bug is probably better than a new, more annoying bug,
> but do you think there's any way to fix the cntrl-z issue while still
> fixing gdb/544?

Woah!  Deterministic behavior on the annotate-quit test?  It's probably
something in the CLI command loop then...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-12 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 15:36 Andrew Cagney
2003-02-12 17:35 ` David Carlton
2003-02-12 18:42   ` Daniel Jacobowitz [this message]
2003-02-12 18:46     ` David Carlton
2003-02-13 17:27       ` Andrew Cagney
2003-02-12 20:04 Michael Elizabeth Chastain
2003-02-12 22:44 Michael Elizabeth Chastain
2003-02-13  1:27 Michael Elizabeth Chastain

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=20030212184232.GA30842@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.redhat.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