From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: gdb-patches@sourceware.org
Cc: uweigand@de.ibm.com, edjunior@gmail.com
Subject: [PATCH v3 01/12] Zero-initialize linux note sections
Date: Tue, 14 Aug 2018 20:07:00 -0000 [thread overview]
Message-ID: <20180814200609.19999-2-pedromfc@linux.ibm.com> (raw)
In-Reply-To: <20180814200609.19999-1-pedromfc@linux.ibm.com>
This patches changes linux-tdep.c so that the buffer used to write
note sections when generating a core file is zero-initialized. This
way, bytes that are not collected won't contain random
data (e.g. padding bytes).
gdb/ChangeLog:
YYYY-MM-DD Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* linux-tdep.c (linux_collect_regset_section_cb): Use
std::vector<char> instead of char * for buf. Remove xfree.
---
gdb/linux-tdep.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
index 3cfa2a5aa4..2bcd2390c5 100644
--- a/gdb/linux-tdep.c
+++ b/gdb/linux-tdep.c
@@ -1583,7 +1583,9 @@ linux_collect_regset_section_cb (const char *sect_name, int size,
const struct regset *regset,
const char *human_name, void *cb_data)
{
- char *buf;
+ /* This is intentionally zero-initialized by using std::vector, so
+ that any padding bytes in the core file will show as 0. */
+ std::vector<char> buf (size);
struct linux_collect_regset_section_cb_data *data
= (struct linux_collect_regset_section_cb_data *) cb_data;
@@ -1592,19 +1594,17 @@ linux_collect_regset_section_cb (const char *sect_name, int size,
gdb_assert (regset && regset->collect_regset);
- buf = (char *) xmalloc (size);
- regset->collect_regset (regset, data->regcache, -1, buf, size);
+ regset->collect_regset (regset, data->regcache, -1, buf.data (), size);
/* PRSTATUS still needs to be treated specially. */
if (strcmp (sect_name, ".reg") == 0)
data->note_data = (char *) elfcore_write_prstatus
(data->obfd, data->note_data, data->note_size, data->lwp,
- gdb_signal_to_host (data->stop_signal), buf);
+ gdb_signal_to_host (data->stop_signal), buf.data ());
else
data->note_data = (char *) elfcore_write_register_note
(data->obfd, data->note_data, data->note_size,
- sect_name, buf, size);
- xfree (buf);
+ sect_name, buf.data (), size);
if (data->note_data == NULL)
data->abort_iteration = 1;
--
2.13.6
next prev parent reply other threads:[~2018-08-14 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 20:07 [PATCH v3 00/12] GDB support for more powerpc registers on linux Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 06/12] [PowerPC] Fix indentation in arch/ppc-linux-common.c Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 04/12] [PowerPC] Remove rs6000_pseudo_register_reggroup_p Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 03/12] Add decfloat registers to float reggroup Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 05/12] [PowerPC] Fix two if statements in gdb/ppc-linux-nat.c Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 07/12] [PowerPC] Refactor have_ initializers in rs6000-tdep.c Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 11/12] [PowerPC] Reject tdescs with VSX and no FPU or Altivec Pedro Franco de Carvalho
2018-08-14 20:07 ` Pedro Franco de Carvalho [this message]
2018-08-14 20:07 ` [PATCH v3 08/12] [PowerPC] Add support for PPR and DSCR Pedro Franco de Carvalho
2018-08-14 20:07 ` [PATCH v3 12/12] [PowerPC] Add support for HTM registers Pedro Franco de Carvalho
2018-08-14 20:10 ` [PATCH v3 00/12] GDB support for more powerpc registers on linux Pedro Franco de Carvalho
2018-08-14 20:41 ` [PATCH v3 09/12] [PowerPC] Add support for TAR Pedro Franco de Carvalho
2018-08-14 20:41 ` [PATCH v3 02/12] [PowerPC] Don't zero-initialize vector register buffers Pedro Franco de Carvalho
2018-08-14 21:13 ` [PATCH v3 10/12] [PowerPC] Add support for EBB and PMU registers Pedro Franco de Carvalho
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=20180814200609.19999-2-pedromfc@linux.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=edjunior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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