From: Mahmood Naderan via Gdb <gdb@sourceware.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>, gdb@sourceware.org
Subject: Re: How to log instructions with GDB
Date: Wed, 10 Mar 2021 13:14:31 +0100 [thread overview]
Message-ID: <CADa2P2XoiJXRqFje4fEYn-VAL3nRQZGo=vgQ7j2AgYTfxeB0wA@mail.gmail.com> (raw)
In-Reply-To: <DM5PR11MB1690D03D9484A8043834A68BDE919@DM5PR11MB1690.namprd11.prod.outlook.com>
I am trying that on virtualbox. I get
(gdb) record btrace
Target does not support branch tracing.
Also, I would like to know where is the file contains "record full"
information?
Regards,
Mahmood
On Wed, Mar 10, 2021 at 12:27 PM Metzger, Markus T <
markus.t.metzger@intel.com> wrote:
> Hello Mahmood,
>
> There's the 'record' command to start recording the execution. By
> default, you'd
> get s/w recording ('record full') that also records data. With 'record
> btrace' you'd
> get a h/w recording solution on systems that support it.
>
> At least 'record btrace' supports 'record instruction-history', which
> should do
> what you're looking for. It is supported on recent IA systems.
>
> There's some documentation on those in the GDB manual.
>
> Regards,
> Markus.
>
> > -----Original Message-----
> > From: Gdb <gdb-bounces@sourceware.org> On Behalf Of Mahmood Naderan via
> > Gdb
> > Sent: Montag, 8. März 2021 15:33
> > To: gdb@sourceware.org
> > Subject: How to log instructions with GDB
> >
> > Hi,
> > I would like to know if GDB has a mechanism to trace the execution
> > instructions while debugging.
> > I am looking for a way to write the executed instructions (similar to the
> > disassembly format) in a file.
> >
> > Regards,
> > Mahmood
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
>
next prev parent reply other threads:[~2021-03-10 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 14:32 Mahmood Naderan via Gdb
[not found] ` <DM5PR11MB1690D03D9484A8043834A68BDE919@DM5PR11MB1690.namprd11.prod.outlook.com>
2021-03-10 12:14 ` Mahmood Naderan via Gdb [this message]
2021-03-10 13:00 ` Metzger, Markus T via Gdb
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='CADa2P2XoiJXRqFje4fEYn-VAL3nRQZGo=vgQ7j2AgYTfxeB0wA@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=mahmood.nt@gmail.com \
--cc=markus.t.metzger@intel.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