Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Hui Zhu" <teawater@gmail.com>, <gdb@sources.redhat.com>,
		"Michael Snyder" <msnyder@vmware.com>
Subject: RE: Reverse debugging
Date: Fri, 17 Jul 2009 02:41:00 -0000	[thread overview]
Message-ID: <19039.58589.853319.841012@totara.tehura.co.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA07BD6DD6@ecamlmw720.eamcs.ericsson.se>

 > So in your case you are dealing with a proper tty?
 > For eclipse, we fall in the !from_tty case.

Emacs communicates with GDB through a pseudo-tty.  How does Eclipse
do it?

This also seems contrary to what Daniel Jacobowitz has previously told me,
perhaps about Eclipse more generally.  CDT has a console and I thought he
assured me that there was interest in developing that functionality.

 > Frontends should definetely not be bothered with those queries.
 > In my mind, a FE should know what it is doing so if it requests
 > an action like 'record stop' it should not be prompted at all.
 > This is probably true for any of these queries.
 > 
 > I was originally going to ask Hui always have a !from_tty check,
 > but now it seems this would not work for emacs.
 > 
 > Can we check if the default interpreter is MI somehow and in those
 > cases not do the query?  The idea is that if one uses MI then
 > it is not in some user-interactive session.
 > 
 > Just a thought...

That might be a good idea but this request isn't for Emacs on trunk, which has
now migrated fully to GDB/MI, but for the release branch which still uses
annotations.  It's just a small request for a slight change to the existing
command "record stop" or, as Hui suggested, adding a special CLI command
to stop recording that doesn't need confirmation.

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


  reply	other threads:[~2009-07-17  2:41 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
2009-07-16  3:09         ` Hui Zhu
2009-07-16 15:55           ` Marc Khouzam
2009-07-17  2:41             ` Nick Roberts [this message]
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=19039.58589.853319.841012@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=marc.khouzam@ericsson.com \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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