Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Marc Khouzam'" <marc.khouzam@ericsson.com>,
		"Tomas Holmberg" <th@virtutech.com>,
		<gdb-patches@sourceware.org>,
		"'Michael Snyder'" <msnyder@vmware.com>
Subject: RE: reverse for GDB/MI
Date: Tue, 16 Dec 2008 08:44:00 -0000	[thread overview]
Message-ID: <026f01c95f5a$657b8920$30729b60$@com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06A3DD92@ecamlmw720.eamcs.ericsson.se>

> 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.

This is to retain compatibility with the normal gdb command-line commands for
reversing. According to an earlier discussion in October, this command was part
of the Michael Snyder patches to support rev exec, and it was decided then not
to change the commands. 
 
> 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.

The simplest solution is to have no "direction" at all, but just a set of
reverse-X and forward-X commands.  But that is not inline with the main gdb user
interface as it stands currently as we understand it. 

Happy to change it, if needed.

Best regards,

/jakob

_______________________________________________________

Jakob Engblom, PhD, Technical Marketing Manager

Virtutech                   Direct: +46 8 690 07 47    
Drottningholmsvägen 14      Mobile: +46 709 242 646   
11243 Stockholm             Web:    www.virtutech.com  
Sweden
________________________________________________________
 




  reply	other threads:[~2008-12-16  8:44 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
2008-12-16  8:44   ` Jakob Engblom [this message]
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='026f01c95f5a$657b8920$30729b60$@com' \
    --to=jakob@virtutech.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --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