Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Jakob Engblom" <jakob@virtutech.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Resubmit, reverse debugging [0/5]
Date: Tue, 14 Oct 2008 09:07:00 -0000	[thread overview]
Message-ID: <daef60380810140206i2fad38ddp720576cb427c5d34@mail.gmail.com> (raw)
In-Reply-To: <003f01c92dd2$32944650$97bcd2f0$@com>

On Tue, Oct 14, 2008 at 15:55, Jakob Engblom <jakob@virtutech.com> wrote:
> Hi!
>
> This is Virtutech weighing in, since our use and implementation of reversibility
> in gbd-serial has come up.  We are perfectly fine with the commands changing a
> little, it is as people have noted not a particularly big deal what the precise
> gdb-serial commands are, as long as they get decided on and remain fixed.  Which
> is exactly why we like the current process of finally seeing reverse execution
> become part of the gdb mainline.
>
> "bc" and "bs" are tried and tested as far as we are concerned, and they appear
> to be still in place from what I can see.
>
> I have another question here: is there a way to check if the remote target does
> support reverse execution? Not all targets will, in our experience. So having
> some way to detect that property of the target is quite useful.

I don't think we need it.
Cause if remote stub don't support "bc" and "bs", it can return empty
rsp package to GDB mean that it don't support this command. GDB can
output warning to user that fail.


>
> 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-10-14  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  2:17 Michael Snyder
2008-10-10 17:44 ` Michael Snyder
2008-10-10 17:54   ` Daniel Jacobowitz
2008-10-10 18:38     ` Michael Snyder
2008-10-11  2:43       ` Daniel Jacobowitz
2008-10-11  2:48         ` Michael Snyder
2008-10-11  8:02           ` Eli Zaretskii
2008-10-13 19:21             ` Michael Snyder
2008-10-14  7:56               ` Jakob Engblom
2008-10-14  9:07                 ` teawater [this message]
2008-10-14 12:24                   ` Daniel Jacobowitz
2008-10-14 12:27           ` Daniel Jacobowitz
2008-10-15 18:20             ` Michael Snyder
2008-10-15 18:30               ` Daniel Jacobowitz
2008-10-15 18:42                 ` Michael Snyder
2008-10-15 18:47                   ` Pedro Alves
2008-10-15 18:49                     ` Michael Snyder
2008-10-11  9:47       ` Joel Brobecker
2008-10-13 19:22         ` Michael Snyder

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=daef60380810140206i2fad38ddp720576cb427c5d34@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jakob@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