public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Xing, Charlie" <Charlie.Xing@Teradata.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Will GDB extract the entire Variable history in further releases, based on Reverse Debugging?
Date: Tue, 29 May 2012 09:31:00 -0000	[thread overview]
Message-ID: <D466CE00251CE745AAE4B3677C6BFD5208D61554@SUSHDC8004.TD.TERADATA.COM> (raw)
In-Reply-To: <4FC39644.8060404@redhat.com>

It comes from a discussion with the CDT team: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg24459.html

I wondered if CDT may provide some features based on the existing Reverse Debugging functionality, they are interested in those features but need GNU GDB to provide more functionality. Therefore I turned to you guys.

I hope the link would make things clearer.

Xing Yun

-----Original Message-----
From: Pedro Alves [mailto:palves@redhat.com] 
Sent: 2012年5月28日 23:14
To: Xing, Charlie
Cc: gdb@sourceware.org
Subject: Re: Will GDB extract the entire Variable history in further releases, based on Reverse Debugging?

On 05/28/2012 02:38 AM, Xing, Charlie wrote:

> Extracting the entire Variable History.

(...)

> Travelling in the Variables History?
(...)


I have to say I didn't really understand what exactly do you mean by those "Variable History" or "Travelling in the Variables History".  Could you elaborate?

--
Pedro Alves

  reply	other threads:[~2012-05-29  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28  1:38 Xing, Charlie
2012-05-28 15:14 ` Pedro Alves
2012-05-29  9:31   ` Xing, Charlie [this message]
2012-05-28 15:28 ` Jan Kratochvil

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=D466CE00251CE745AAE4B3677C6BFD5208D61554@SUSHDC8004.TD.TERADATA.COM \
    --to=charlie.xing@teradata.com \
    --cc=gdb@sourceware.org \
    --cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).