Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Doug Evans <dje@google.com>
Cc: Pedro Alves <palves@redhat.com>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: RE: [rfc] btrace: change record instruction-history /m
Date: Mon, 17 Aug 2015 07:23:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2333193E67@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <CADPb22R4MY9rv62NmVvJ6=0064TW7nC=ghoChqHJ4Hs7aCkXrQ@mail.gmail.com>

> -----Original Message-----
> From: Doug Evans [mailto:dje@google.com]
> Sent: Friday, August 14, 2015 7:02 PM
> To: Metzger, Markus T
> Cc: Pedro Alves; gdb-patches
> Subject: Re: [rfc] btrace: change record instruction-history /m


> > Alternatively, we could extend Doug Evan's new algorithm
> > https://sourceware.org/ml/gdb-patches/2015-08/msg00335.html to take a
> vector
> > of PCs.
> >
> > 2015-08-14  Markus Metzger <markus.t.metzger@intel.com>
> >
> > gdb/
> >         * record-btrace.c (struct btrace_line_range): New.
> >         (btrace_mk_line_range, btrace_line_range_add)
> >         (btrace_line_range_is_empty, btrace_line_range_contains_range)
> >         (btrace_find_line_range, btrace_print_lines): New.
> >         (btrace_insn_history): Add source interleaving algorithm.
> 
> Yeah, I'd like to avoid having multiple copies of code
> doing basically the same thing.
> Plus, no one is going to look in record-btrace.c for
> "smart disassembly support".
> disasm.c should be providing the necessary API
> that the rest of gdb an use.

OK, I'll look into it.  I have a few other things to do first.

I wouldn't get too fancy, though, and simply replace the low/high
PC pair with a vector of PCs.  We may have a small wrapper that
generates the vector out of a low/high pair to keep the original
API.

Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  parent reply	other threads:[~2015-08-17  7:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 11:37 Markus Metzger
2015-08-14 13:45 ` Eli Zaretskii
2015-08-14 17:06   ` Doug Evans
2015-08-14 20:32     ` Eli Zaretskii
2015-08-17  7:16       ` Metzger, Markus T
2015-08-17 15:10         ` Eli Zaretskii
2015-08-18  6:30           ` Metzger, Markus T
2015-08-18 14:22             ` Eli Zaretskii
2015-08-14 17:02 ` Doug Evans
2015-08-14 17:44   ` Doug Evans
2015-08-17  7:23   ` Metzger, Markus T [this message]
2015-08-18 14:57 ` Pedro Alves
2015-08-19 14:45   ` Marc Khouzam

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=A78C989F6D9628469189715575E55B2333193E67@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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