Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Using bt command in async mode
Date: Fri, 11 Apr 2008 22:55:00 -0000	[thread overview]
Message-ID: <18431.58411.357257.512508@kahikatea.snap.net.nz> (raw)
In-Reply-To: <ftldhf$1v0$1@ger.gmane.org>

 > > Incidentally, the patch I've presented for bt isn't suitable for inclusion
 > > as it uses:
 > > 
 > > +
 > > +   if (restart)
 > > +     continue_command ("&", 0);
 > > 
 > > If the user interrupts with 'bt' during a step, he presumably wants the
 > > step to finish.  I'm not sure how easy it is for Gdb to jump the inferior
 > > back into it's old state of execution.
 > 
 > It's not very hard. You only need to hack continue_command not to call
 > (indirectly) the clear_proceed_status function, which currently wipes away
 > all state.

It looks a bit harder than that.  Perhaps the arguments proceed () was called
with need to be saved, as well as executing the appropriate contination
after proceed () returns.

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


  reply	other threads:[~2008-04-11 22:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  2:08 Nick Roberts
2008-04-01 19:55 ` Tom Tromey
2008-04-01 22:30   ` Nick Roberts
2008-04-10 16:05     ` Vladimir Prus
2008-04-11 22:55       ` Nick Roberts [this message]
2008-04-10 15:22   ` Daniel Jacobowitz
2008-04-10 15:36     ` Tom Tromey
2008-04-10 15:39       ` Pedro Alves
2008-04-17  2:58         ` Tom Tromey
2008-04-10 15:53       ` Daniel Jacobowitz
2008-04-17  2:47       ` Tom Tromey

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