Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Tomas Holmberg" <th@virtutech.com>, <gdb-patches@sourceware.org>,
	        "Michael Snyder" <msnyder@vmware.com>
Subject: RE: reverse for GDB/MI
Date: Mon, 15 Dec 2008 18:52:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06A3DD92@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <49463870.6080302@virtutech.com>

Hi,

Looking forward to having MI support for reverse debugging.

One little annoying point is the command
-gdb-set exec-direction [forward | reverse]
When this command is issued, to be really correct, MI would need an
event to notify a frontend that the exec-direction has changed.
This is in case the exec-direction is changed in the console or from
another window.

Another option, to avoid adding a new event, is if we could disable the
changing of exec-direction when running in MI, and simulate it in the
frontend.
The frontend could simply keep track of the exec-direction chosen by the
user 
and issue reverse commands or forward commands, appropriately.

Just a thought.

marc



> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Tomas Holmberg
> Sent: Monday, December 15, 2008 5:59 AM
> To: gdb-patches@sourceware.org; Michael Snyder
> Subject: reverse for GDB/MI
> 
> Hi,
> 
> I have looked at the new reverse functionality in GDB and I think that
> it looks really good. I would like to see the reverse commands in the
> GDB/MI interface as well. I have attached two patches with the same
> purpose, to add reverse commands to the MI interface, as I am not sure
> which one that is best.
> 
> /Tomas Holmberg
> 


  reply	other threads:[~2008-12-15 18:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 10:59 Tomas Holmberg
2008-12-15 18:52 ` Marc Khouzam [this message]
2008-12-16  8:44   ` Jakob Engblom
2008-12-16 14:45     ` Marc Khouzam
2008-12-15 20:50 ` Eli Zaretskii
2008-12-17 14:57   ` Tomas Holmberg
2008-12-17 16:41     ` Eli Zaretskii
2008-12-17 16:17 ` Vladimir Prus
2008-12-18  8:33   ` Tomas Holmberg
2008-12-18  8:35     ` Vladimir Prus
2008-12-18  9:16       ` Jakob Engblom
2009-02-05  9:38         ` Vladimir Prus
2009-02-06  4:11           ` Doug Evans
2009-02-06 10:08           ` Jakob Engblom
2009-02-06 10:49             ` Vladimir Prus
2009-02-06 13:56               ` Jakob Engblom
2008-12-19  8:26       ` Tomas Holmberg
2008-12-19 11:07         ` Joel Brobecker
2008-12-19 13:22           ` Pedro Alves
2008-12-19 13:32             ` Jakob Engblom
2008-12-19 19:11         ` Michael Snyder
2008-12-22 20:27           ` Marc Khouzam
2008-12-22 21:14             ` Michael Snyder
2008-12-22 21:16               ` Marc Khouzam
2009-01-03 18:09             ` Jakob Engblom
2009-01-20 18:22               ` Marc Khouzam
2009-01-21  5:23                 ` teawater
2009-01-21 15:21                 ` Tomas Holmberg
2009-02-05 12:08                 ` Vladimir Prus
2008-12-18 21:39     ` Michael Snyder
2008-12-19  9:10       ` Tomas Holmberg

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=6D19CA8D71C89C43A057926FE0D4ADAA06A3DD92@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=th@virtutech.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