From: Markus Metzger <markus.t.metzger@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com
Subject: [PATCH 0/5] improve trace gap handling
Date: Fri, 22 Jul 2016 08:12:00 -0000 [thread overview]
Message-ID: <1469175120-19657-1-git-send-email-markus.t.metzger@intel.com> (raw)
A small patch series that improves dealing with gaps in recorded trace.
Markus Metzger (5):
btrace: fix gap indication
btrace: allow leading trace gaps
btrace: update tail call heuristic
btrace: preserve function level for unexpected returns
btrace: bridge gaps
gdb/btrace.c | 531 ++++++++++++++++++++++++++++++++++++++++++++++------
gdb/record-btrace.c | 33 +++-
2 files changed, 503 insertions(+), 61 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-07-22 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 8:12 Markus Metzger [this message]
2016-07-22 8:12 ` [PATCH 2/5] btrace: allow leading trace gaps Markus Metzger
2016-07-22 8:12 ` [PATCH 3/5] btrace: update tail call heuristic Markus Metzger
2016-07-22 8:12 ` [PATCH 5/5] btrace: bridge gaps Markus Metzger
2016-07-22 8:12 ` [PATCH 4/5] btrace: preserve function level for unexpected returns Markus Metzger
2016-10-27 10:59 ` [PATCH 0/5] improve trace gap handling Yao Qi
2016-10-27 12:39 ` Metzger, Markus T
2016-10-27 15:04 ` Yao Qi
2016-10-27 15:11 ` Pedro Alves
2016-10-28 7:11 ` Metzger, Markus T
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=1469175120-19657-1-git-send-email-markus.t.metzger@intel.com \
--to=markus.t.metzger@intel.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