Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: kdevelop@kdevelop.org, gdb@sources.redhat.com
Subject: Re: 'continue' command problem
Date: Mon, 25 Jun 2007 07:51:00 -0000	[thread overview]
Message-ID: <18047.29700.556363.455690@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200706251101.54544.ghost@cs.msu.su>

 > Nick, 
 > I think your "async branch" is supposed to emit "^running" in all possible
 > cases.  Is that the case, and if so, do you think that improvement can be
 > ported to gdb mainline quickly?

I've abandoned the branch but have a much smaller patch that does something
similar.  It should emit all asynchronous records but I'm not sure what
what happens inside a user-defined command.

It's not really a quick fix for a specific problem but a different approach
to a more general one.  The patch is at:

http://sourceware.org/ml/gdb-patches/2006-11/msg00225.html

and there has been more recent discussion about it on gdb-patches this month
(Re: async patch (no. 4)).

I have a working copy so I can send you a current patch privately if you want
to try it out.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-06-25  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200706041421.21962.leonp@plris.com>
2007-06-25  7:02 ` Vladimir Prus
2007-06-25  7:51   ` Nick Roberts [this message]
2007-06-25 18:04   ` Jim Ingham
2007-06-26  4:40     ` Nick Roberts
2007-06-26 18:16       ` Jim Ingham
2007-06-27  0:12         ` Nick Roberts
2007-06-26  7:13     ` Vladimir Prus

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=18047.29700.556363.455690@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=kdevelop@kdevelop.org \
    /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