From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] Fetch all registers before writing the core register notes.
Date: Sat, 14 Mar 2015 22:02:00 -0000 [thread overview]
Message-ID: <2653052.Cuv9hkMi4i@ralph.baldwin.cx> (raw)
Without this, not all registers were present in the core generated by gcore.
For example, running 'gcore' on a program without examining the vector
registers (SSE or AVX) would store all the vector registers as zeros because
they were not pulled into the regcache. Running 'info vector' before 'gcore'
would store the correct values in the core since it populated the regcache.
For Linux processes, a similar operation is achieved somewhat by having the
thread iterator callback invoke target_fetch_registers on each thread before
its corresponding register notes are dumped.
(I don't plan on including that level of detail in the commit log, just as
a way to explain the bug this change fixes.)
gdb/ChangeLog:
* fbsd-tdep.c (fbsd_make_corefile_notes): Fetch all target registers
before writing core register notes.
---
diff --git a/gdb/fbsd-tdep.c b/gdb/fbsd-tdep.c
index 5d17f03..9609cd8 100644
--- a/gdb/fbsd-tdep.c
+++ b/gdb/fbsd-tdep.c
@@ -89,7 +89,7 @@ fbsd_collect_regset_section_cb (const char *sect_name, int size,
static char *
fbsd_make_corefile_notes (struct gdbarch *gdbarch, bfd *obfd, int *note_size)
{
- const struct regcache *regcache = get_current_regcache ();
+ struct regcache *regcache = get_current_regcache ();
char *note_data;
Elf_Internal_Ehdr *i_ehdrp;
struct fbsd_collect_regset_section_cb_data data;
@@ -104,6 +104,7 @@ fbsd_make_corefile_notes (struct gdbarch *gdbarch, bfd *obfd, int *note_size)
data.obfd = obfd;
data.note_data = NULL;
data.note_size = note_size;
+ target_fetch_registers (regcache, -1);
gdbarch_iterate_over_regset_sections (gdbarch,
fbsd_collect_regset_section_cb,
&data, regcache);
--
2.2.1
next reply other threads:[~2015-03-14 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 22:02 John Baldwin [this message]
2015-03-16 12:09 ` Pedro Alves
2015-03-16 14:55 ` John Baldwin
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=2653052.Cuv9hkMi4i@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--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