From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Change target stack representation
Date: Mon, 28 May 2018 16:10:00 -0000 [thread overview]
Message-ID: <20180528161041.32497-1-palves@redhat.com> (raw)
Another week, another piece off of the multi-target branch.
This is preparation for being able to have multiple target stacks in
GDB, so that we can have a target stack for inferior 1 debugging a
core, a target stack for inferior 2 debugging a native process, a
target stack for inferior 3 debugging a remote process, etc.
More details in the individual patches.
Pedro Alves (4):
target_stack -> current_top_target() throughout
target_ops::beneath -> target_ops::beneath()
Eliminate find_target_beneath
Introduce class target_stack
gdb/aix-thread.c | 29 +-
gdb/auxv.c | 4 +-
gdb/avr-tdep.c | 4 +-
gdb/breakpoint.c | 7 +-
gdb/bsd-uthread.c | 18 +-
gdb/corefile.c | 2 +-
gdb/corelow.c | 8 +-
gdb/elfread.c | 9 +-
gdb/eval.c | 2 +-
gdb/exceptions.c | 2 +-
gdb/frame.c | 2 +-
gdb/gdbarch-selftests.c | 2 +-
gdb/gnu-v3-abi.c | 2 +-
gdb/ia64-tdep.c | 2 +-
gdb/ia64-vms-tdep.c | 2 +-
gdb/infcall.c | 7 +-
gdb/infcmd.c | 18 +-
gdb/infrun.c | 12 +-
gdb/linespec.c | 2 +-
gdb/linux-tdep.c | 19 +-
gdb/linux-thread-db.c | 24 +-
gdb/make-target-delegates | 8 +-
gdb/mi/mi-main.c | 8 +-
gdb/minsyms.c | 5 +-
gdb/ppc-linux-nat.c | 2 +-
gdb/ppc-linux-tdep.c | 4 +-
gdb/procfs.c | 2 +-
gdb/ravenscar-thread.c | 39 +-
gdb/record-btrace.c | 38 +-
gdb/record-full.c | 44 +-
gdb/regcache.c | 4 +-
gdb/remote.c | 16 +-
gdb/rs6000-tdep.c | 2 +-
gdb/s390-linux-nat.c | 2 +-
gdb/s390-tdep.c | 2 +-
gdb/sol-thread.c | 32 +-
gdb/solib-aix.c | 2 +-
gdb/solib-darwin.c | 4 +-
gdb/solib-dsbt.c | 4 +-
gdb/solib-spu.c | 6 +-
gdb/solib-svr4.c | 23 +-
gdb/solib-target.c | 3 +-
gdb/sparc-tdep.c | 2 +-
gdb/sparc64-tdep.c | 4 +-
gdb/spu-multiarch.c | 33 +-
gdb/spu-tdep.c | 32 +-
gdb/symfile.c | 2 +-
gdb/symtab.c | 7 +-
gdb/target-delegates.c | 1280 ++++++++++++++++++++++-----------------------
gdb/target-descriptions.c | 4 +-
gdb/target-memory.c | 4 +-
gdb/target.c | 361 ++++++-------
gdb/target.h | 211 +++++---
gdb/tracefile-tfile.c | 2 +-
gdb/tracepoint.c | 2 +-
gdb/valops.c | 4 +-
gdb/valprint.c | 2 +-
gdb/value.c | 2 +-
gdb/windows-tdep.c | 2 +-
59 files changed, 1177 insertions(+), 1204 deletions(-)
--
2.14.3
next reply other threads:[~2018-05-28 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 16:10 Pedro Alves [this message]
2018-05-28 16:10 ` [PATCH 1/4] target_stack -> current_top_target() throughout Pedro Alves
2018-05-29 3:13 ` Tom Tromey
2018-05-28 16:19 ` [PATCH 2/4] target_ops::beneath -> target_ops::beneath() Pedro Alves
2018-05-28 17:39 ` [PATCH 3/4] Eliminate find_target_beneath Pedro Alves
2018-05-28 17:47 ` [PATCH 4/4] Introduce class target_stack Pedro Alves
2018-05-29 11:34 ` Tom Tromey
2018-05-29 14:59 ` Pedro Alves
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=20180528161041.32497-1-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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