Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Hui Zhu <teawater@gmail.com>
Cc: Michael Snyder <msnyder@vmware.com>,
		"gdb@sources.redhat.com" <gdb@sources.redhat.com>
Subject: Re: Reverse debugging
Date: Fri, 17 Jul 2009 02:32:00 -0000	[thread overview]
Message-ID: <19039.58021.757138.220152@totara.tehura.co.nz> (raw)
In-Reply-To: <daef60380907152005v762006d2vc1a913c2046b4767@mail.gmail.com>

 > > ...If I try to reverse a remote target using gdbserver (actually on
 > > host/local machine - x86_64 this time), I'm not told that the target
 > > doesn't support this command but reverse-next works just like next until
 > > I hit a function:
 > >
 > > (gdb) reverse-next
 > >
 > > Program received signal SIGTRAP, Trace/breakpoint trap.
 > > 0x0000000000400521 in printf@plt ()
 > > Current language:  auto; currently asm
 > > (gdb)
 > 
 > Looks like you use an old gdb-cvs version with amd64,right?

I didn't think I had an old gdb-cvs version - at least not more than a few
days old.

 > 1. Please use the head version of gdb.  It will tell you that amd64
 > doesn't support prec now.

I've tried it again and it does, indeed, report it.  Thanks.

 > 2. You can try the patch that I post to make gdb support amd64.  You
 > can get the link and other message from
 > http://sourceware.org/gdb/wiki/ReversibleDebugging

I can try it if you wish but I don't have access to any real embedded
targets and have only used "target remote" through gdbserver on my local
machine.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2009-07-17  2:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  0:40 Nick Roberts
2009-07-14  0:53 ` Michael Snyder
2009-07-14  1:28   ` Nick Roberts
2009-07-14 17:36     ` Michael Snyder
2009-07-15  2:28       ` Nick Roberts
2009-07-16  3:09         ` Hui Zhu
2009-07-16 15:55           ` Marc Khouzam
2009-07-17  2:41             ` Nick Roberts
2009-07-17 14:12               ` Marc Khouzam
2009-07-17 14:25                 ` Daniel Jacobowitz
2009-07-17 14:56                   ` Marc Khouzam
2009-07-17 15:02                     ` Daniel Jacobowitz
2009-07-19  3:21                   ` Marc Khouzam
2009-07-20  3:27                     ` Hui Zhu
2009-07-20 12:50                       ` Marc Khouzam
2009-07-20 13:19                         ` Marc Khouzam
2009-07-20 14:51                           ` Hui Zhu
2009-07-21  3:21                             ` Marc Khouzam
2009-09-11 13:26                       ` Marc Khouzam
2009-07-18  1:06                 ` Nick Roberts
2009-07-18  4:00                   ` Daniel Jacobowitz
2009-07-22 17:46                     ` Marc Khouzam
2009-07-16  3:05     ` Hui Zhu
2009-07-17  2:32       ` Nick Roberts [this message]
2009-08-17  7:49   ` Jakob Engblom

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=19039.58021.757138.220152@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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