From: teawater <teawater@gmail.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: Jakob Engblom <jakob@virtutech.com>, gdb-patches@sources.redhat.com
Subject: Re: reverse for GDB/MI
Date: Wed, 21 Jan 2009 05:23:00 -0000 [thread overview]
Message-ID: <daef60380901202123q923ebf0pd7c90d5c51856fa2@mail.gmail.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06CB06BB@ecamlmw720.eamcs.ericsson.se>
Thanks for the great work that your guys doing. :)
On Wed, Jan 21, 2009 at 02:19, Marc Khouzam <marc.khouzam@ericsson.com> wrote:
> Hi,
>
> I am hoping this request can help restart the process
> of getting the reverse MI commands approved.
>
> I have applied the patches of Process Record and Replay
> and have built myself a nice GDB that can do reverse debugging
> on Linux.
>
> I then implemented the corresponding support in DSF-GDB
> (soon to be committed.) However, I ran into some MI limitations
> (explanation below for those interested) which make me need
> the MI Commands for Reverse debugging.
>
> A patch for these commands was submitted in
> http://sourceware.org/ml/gdb-patches/2008-12/msg00276.html
> but there were many discussions after, which did not seem to
> conclude.
>
> The details of my troubles follow:
>
> With no MI commands for Reverse I tried to use CLI commands
> but ran into a bug causing incomplete MI *stopped event when using CLI commands.
> http://sourceware.org/ml/gdb/2008-12/msg00058.html
>
> As per Nick's finding, I tried Async mode to work around *stopped event bug but
> realized Process Record and Replay does not support Async.
>
> So, the solution I currently have is to use "set execution-direction" and the
> MI commands for execution. For example, to perform a 'reverse-continue' from
> DSF-GDB I have to do the set of three commands:
>
> set execution-direction reverse
> -exec-continue
> set execution-direction forward
>
> It would be nice to have the reverse MI commands :-)
>
> Thanks
>
> Marc
>
>> -----Original Message-----
>> From: gdb-patches-owner@sourceware.org
>> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Jakob Engblom
>> Sent: Saturday, January 03, 2009 1:09 PM
>> To: gdb-patches@sources.redhat.com
>> Subject: RE: reverse for GDB/MI
>>
>>
>> > Hi,
>> >
>> > It was pointed out to me that people who have been doing reversible
>> > debug for a while seems to
>> > have specific commands for reverse debugging and they do
>> have a command
>> > for "go to time point P".
>> > For example http://www.undo-software.com/undodb_man.html:
>> >
>> > bgoton <number>
>> > Move forwards or backwards to the specified time, in simulated
>> > nanoseconds.
>> > bgoton +<number> | -<number>
>> > Step forward/backward the specified number of simulated nanoseconds.
>>
>> Simics has it to, in some different ways:
>>
>> skip-to <bookmark>
>> reverse n time units
>> continue n time units
>>
>> I think this is a good example of the kind of new commands
>> and abilities that
>> come with having a reverse ability in the first place, like
>> Marc said.
>>
>> And as the later discussion evolved, it would be jolly nice
>> to have an idea of
>> time in gdb. I think that is needed anyway to handle
>> multicore, multiprocessor,
>> and multithreaded debug: when things happen in disparate
>> locations under the
>> control of a single debugger quickly gets very interesting...
>>
>> 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
>> ________________________________________________________
>>
>>
>>
>>
>
next prev parent reply other threads:[~2009-01-21 5:23 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
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 [this message]
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=daef60380901202123q923ebf0pd7c90d5c51856fa2@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jakob@virtutech.com \
--cc=marc.khouzam@ericsson.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