From: markus.t.metzger@intel.com
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org, markus.t.metzger@gmail.com,
Markus Metzger <markus.t.metzger@intel.com>
Subject: [rfc 0/8] refactor record
Date: Thu, 14 Feb 2013 16:31:00 -0000 [thread overview]
Message-ID: <1360859352-30399-1-git-send-email-markus.t.metzger@intel.com> (raw)
From: Markus Metzger <markus.t.metzger@intel.com>
Hi Jan,
Here's an updated version of the record.c refactoring incorporating your
comments and adding two new commands I plan to implement for record-btrace.
The series will not apply to the current master since i'm not resending some
already approved patches.
I tried pushing the entire series into archer but I seem to lack permissions.
I ran the gdb.reverse suite without regressions on 64bit IA gnu/linux.
Markus Metzger (8):
record: make it build again
record-full.c: rename record_ in record_full_.
record-full.h: rename record_ into record_full_
record: default target methods.
record: add "record disassemble" command
record disas: omit function names by default
record: add "record backtrace" command
record: add "record list" command
gdb/Makefile.in | 5 +-
gdb/amd64-linux-tdep.c | 53 +-
gdb/arm-tdep.c | 12 +-
gdb/i386-linux-tdep.c | 30 +-
gdb/i386-tdep.c | 465 +++++++-------
gdb/infrun.c | 3 +-
gdb/linux-record.c | 544 ++++++++-------
gdb/moxie-tdep.c | 85 ++--
gdb/record-full.c | 1775 ++++++++++++++++++++++++++++--------------------
gdb/record-full.h | 10 +-
gdb/record.c | 696 ++++++++++++++-----
gdb/record.h | 30 +
gdb/target.c | 231 +++++++
gdb/target.h | 81 +++
14 files changed, 2505 insertions(+), 1515 deletions(-)
next reply other threads:[~2013-02-14 16:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 16:31 markus.t.metzger [this message]
2013-02-14 16:30 ` [rfc 5/8] record: add "record disassemble" command markus.t.metzger
2013-02-14 16:30 ` [rfc 4/8] record: default target methods markus.t.metzger
2013-02-14 16:30 ` [rfc 7/8] record: add "record backtrace" command markus.t.metzger
2013-02-14 16:30 ` [rfc 6/8] record disas: omit function names by default markus.t.metzger
2013-02-15 16:11 ` Jan Kratochvil
2013-02-15 18:21 ` Eli Zaretskii
2013-02-15 18:33 ` Jan Kratochvil
2013-02-15 19:05 ` Eli Zaretskii
2013-02-15 19:10 ` Jan Kratochvil
2013-02-18 9:43 ` Metzger, Markus T
2013-02-18 13:03 ` Jan Kratochvil
2013-02-18 13:30 ` Metzger, Markus T
2013-02-18 14:13 ` Jan Kratochvil
2013-02-18 14:51 ` Metzger, Markus T
2013-02-18 15:54 ` Jan Kratochvil
2013-02-19 8:34 ` Metzger, Markus T
2013-02-19 8:52 ` [RFC on command names] " Jan Kratochvil
2013-02-18 16:17 ` Eli Zaretskii
2013-02-15 20:43 ` Tom Tromey
2013-02-14 16:30 ` [rfc 8/8] record: add "record list" command markus.t.metzger
2013-02-14 16:31 ` [rfc 3/8] record-full.h: rename record_ into record_full_ markus.t.metzger
2013-02-14 16:31 ` [rfc 2/8] record-full.c: rename record_ in record_full_ markus.t.metzger
2013-02-15 8:45 ` Jan Kratochvil
2013-02-14 16:32 ` [rfc 1/8] record: make it build again markus.t.metzger
2013-02-15 11:18 ` [rfc 0/8] refactor record Metzger, Markus T
2013-02-15 16:15 ` Jan Kratochvil
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=1360859352-30399-1-git-send-email-markus.t.metzger@intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=markus.t.metzger@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