Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sources.redhat.com" <gdb@sources.redhat.com>
Subject: Re: Reverse debugging
Date: Wed, 15 Jul 2009 02:28:00 -0000	[thread overview]
Message-ID: <19037.16041.589932.535743@totara.tehura.co.nz> (raw)
In-Reply-To: <4A5CC0E1.7020800@vmware.com>

I've created tool bar functionality in Emacs for reverse debugging a bit like
that in the DSF-GDB debugger for Eclipse, I think.

It works quite nicely and I would like to include it in Emacs 23.2 (23.1
should be coming out next week) but there is one small problem with "record
stop".  It currently prompts the user for confirmation and Emacs can't handle
that from the tool bar and update the GUI.  Would it be possible to add a
"noconfirm" option, perhaps like below, which should be invisible to the
normal user?

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


2009-07-15  Nick Roberts  <nickrob@snap.net.nz>

	* record.c (cmd_record_stop): Add a "noconfirm" option to the
	"record stop" command.


Index: record.c
===================================================================
RCS file: /cvs/src/src/gdb/record.c,v
retrieving revision 1.8
diff -c -p -r1.8 record.c
*** record.c	2 Jul 2009 17:21:06 -0000	1.8
--- record.c	15 Jul 2009 02:25:21 -0000
*************** cmd_record_stop (char *args, int from_tt
*** 1157,1164 ****
  {
    if (current_target.to_stratum == record_stratum)
      {
!       if (!record_list || !from_tty || query (_("Delete recorded log and "
! 	                                        "stop recording?")))
  	unpush_target (&record_ops);
      }
    else
--- 1157,1168 ----
  {
    if (current_target.to_stratum == record_stratum)
      {
!       int noconfirm = 0;
!       if (args)
!         noconfirm = (strcmp (args, "noconfirm") == 0) ? 1 : 0;
! 	
!       if (!record_list || !from_tty || noconfirm
! 	  || query (_("Delete recorded log and stop recording?")))
  	unpush_target (&record_ops);
      }
    else


  reply	other threads:[~2009-07-15  2:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  0:40 Nick Roberts
2009-07-14  0:53 ` Michael Snyder
2009-07-14  1:28   ` Nick Roberts
2009-07-14 17:36     ` Michael Snyder
2009-07-15  2:28       ` Nick Roberts [this message]
2009-07-16  3:09         ` Hui Zhu
2009-07-16 15:55           ` Marc Khouzam
2009-07-17  2:41             ` Nick Roberts
2009-07-17 14:12               ` Marc Khouzam
2009-07-17 14:25                 ` Daniel Jacobowitz
2009-07-17 14:56                   ` Marc Khouzam
2009-07-17 15:02                     ` Daniel Jacobowitz
2009-07-19  3:21                   ` Marc Khouzam
2009-07-20  3:27                     ` Hui Zhu
2009-07-20 12:50                       ` Marc Khouzam
2009-07-20 13:19                         ` Marc Khouzam
2009-07-20 14:51                           ` Hui Zhu
2009-07-21  3:21                             ` Marc Khouzam
2009-09-11 13:26                       ` Marc Khouzam
2009-07-18  1:06                 ` Nick Roberts
2009-07-18  4:00                   ` Daniel Jacobowitz
2009-07-22 17:46                     ` Marc Khouzam
2009-07-16  3:05     ` Hui Zhu
2009-07-17  2:32       ` Nick Roberts
2009-08-17  7:49   ` Jakob Engblom

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=19037.16041.589932.535743@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@vmware.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