From: Roman Pen <roman.penyaev@profitbricks.com>
Cc: Roman Pen <roman.penyaev@profitbricks.com>,
Pedro Alves <palves@redhat.com>,
Daniel Jacobowitz <dan@codesourcery.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH 1/1] [RFC] gdb: corelow: make possible to modify (set) registers for a corefile
Date: Tue, 14 Mar 2017 10:09:00 -0000 [thread overview]
Message-ID: <20170314100838.12647-1-roman.penyaev@profitbricks.com> (raw)
Despite the fact that this is a hairy hack this change eases debugging
of a jmp_buf (setjmp()) and user contexts (makecontext()), which are
highly used in QEMU project as a part of coroutines.
This change allows setting registers for a corefile, thus QEMU gdb
script (qemu/scripts/qemugdb/coroutine.py) is allowed to investigate
backtrace of a preempted coroutine context. Previously only debugging
of a live process was allowed.
This patch caches all register on a first attempt to modify register
'(gdb) set $REG = ADDR' and then cached copy is always returned from
get_core_registers().
This change should not break previous behaviour if nobody sets any
register, i.e. on each get_core_registers() call registers from a
corefile will be reread.
Signed-off-by: Roman Pen <roman.penyaev@profitbricks.com>
Cc: Pedro Alves <palves@redhat.com>
Cc: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
QEMU guys who can be interested in this new gdb behaviour:
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
---
gdb/corelow.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
diff --git a/gdb/corelow.c b/gdb/corelow.c
index c46af0a8a59d..4a4b20ed57a0 100644
--- a/gdb/corelow.c
+++ b/gdb/corelow.c
@@ -74,6 +74,15 @@ static struct gdbarch *core_gdbarch = NULL;
unix child targets. */
static struct target_section_table *core_data;
+/* Cached registers. Once registers are modified (set) for a corefile,
+ they are cached and then are always fetched from get_core_registers().
+ This hairy hack is used only for one purpose: give a possibility to
+ debug jmp_buf (setjmp()) and user contexts (makecontext()). */
+
+static struct cached_reg {
+ char regp[MAX_REGISTER_SIZE];
+} *core_cachedregs;
+
static void core_files_info (struct target_ops *);
static struct core_fns *sniff_core_bfd (bfd *);
@@ -213,6 +222,11 @@ core_close (struct target_ops *self)
}
core_vec = NULL;
core_gdbarch = NULL;
+ if (core_cachedregs)
+ {
+ xfree(core_cachedregs);
+ core_cachedregs = NULL;
+ }
}
static void
@@ -620,6 +634,18 @@ get_core_registers (struct target_ops *ops,
}
gdbarch = get_regcache_arch (regcache);
+
+ if (core_cachedregs)
+ {
+ /* If registers were once modified (set) for a corefile,
+ follow this path and always return cached registers */
+
+ for (i = 0; i < gdbarch_num_regs(gdbarch); i++)
+ regcache_raw_supply(regcache, i, &core_cachedregs[i]);
+
+ return;
+ }
+
if (gdbarch_iterate_over_regset_sections_p (gdbarch))
gdbarch_iterate_over_regset_sections (gdbarch,
get_core_registers_cb,
@@ -639,6 +665,29 @@ get_core_registers (struct target_ops *ops,
}
static void
+set_core_registers (struct target_ops *self, struct regcache *regcache,
+ int regnum)
+{
+ struct gdbarch *gdbarch;
+ int i;
+
+ gdbarch = get_regcache_arch(regcache);
+
+ if (core_cachedregs == NULL)
+ core_cachedregs = (struct cached_reg*)xcalloc(gdbarch_num_regs(gdbarch),
+ sizeof(*core_cachedregs));
+
+ for (i = 0; i < gdbarch_num_regs(gdbarch); i++)
+ regcache_raw_collect(regcache, i, &core_cachedregs[i]);
+}
+
+static void
+prepare_core_registers (struct target_ops *self, struct regcache *arg1)
+{
+ /* nothing here */
+}
+
+static void
core_files_info (struct target_ops *t)
{
print_section_info (core_data, core_bfd);
@@ -1050,6 +1099,8 @@ init_core_ops (void)
core_ops.to_close = core_close;
core_ops.to_detach = core_detach;
core_ops.to_fetch_registers = get_core_registers;
+ core_ops.to_store_registers = set_core_registers;
+ core_ops.to_prepare_to_store = prepare_core_registers;
core_ops.to_xfer_partial = core_xfer_partial;
core_ops.to_files_info = core_files_info;
core_ops.to_insert_breakpoint = ignore;
--
2.11.0
next reply other threads:[~2017-03-14 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 10:09 Roman Pen [this message]
2017-03-14 13:15 ` Ulrich Weigand
2017-03-15 9:02 ` Roman Penyaev
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=20170314100838.12647-1-roman.penyaev@profitbricks.com \
--to=roman.penyaev@profitbricks.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@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