From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] valprint.c (read_string): Rework clean-up logic.
Date: Fri, 27 Feb 2009 19:41:00 -0000 [thread overview]
Message-ID: <49A82F5C.9000801@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hi,
While performing some Valgrind profiling on GDB we found that the
"read_string" function in valprint.c can leak clean-ups. This happens
as it does not account for a previous clean-up in the local chain and
overwrites the local "old_chain" place holder with a new one. This patch
reworks the function's clean-up logic, only registering one clean-up at
the beginning and including a new clean-up function. This new clean-up
function frees buffers referenced by double indirection.
This patch neither increases or decreases regressions in the test-suite.
It was built and tested on X86_64.
2009-02-27 Phil Muldoon <pmuldoon@redhat.com>
* valprint.c (xfree_gdb_byte): New function.
(read_string): Rework clean-up logic. Use xfree_gdb_byte for
clean-up.
[-- Attachment #2: read_string_cleanup-cvs.patch --]
[-- Type: text/x-patch, Size: 1844 bytes --]
Index: gdb/valprint.c
===================================================================
RCS file: /cvs/src/src/gdb/valprint.c,v
retrieving revision 1.79
diff -u -r1.79 valprint.c
--- gdb/valprint.c 5 Feb 2009 12:16:25 -0000 1.79
+++ gdb/valprint.c 27 Feb 2009 17:55:46 -0000
@@ -1177,6 +1177,15 @@
return (nread);
}
+/* Local clean-up for a gdb_byte buffer pointed to via double
+ indirection. This function is used in read_string. */
+static void
+xfree_gdb_byte (void *buffer)
+{
+ gdb_byte **pointer = buffer;
+ xfree (*pointer);
+}
+
/* Read a string from the inferior, at ADDR, with LEN characters of WIDTH bytes
each. Fetch at most FETCHLIMIT characters. BUFFER will be set to a newly
allocated buffer containing the string, which the caller is responsible to
@@ -1226,13 +1235,14 @@
some error, such as bumping into the end of the address space. */
found_nul = 0;
- old_chain = make_cleanup (null_cleanup, 0);
+ *buffer = NULL;
+
+ old_chain = make_cleanup (xfree_gdb_byte, buffer);
if (len > 0)
{
*buffer = (gdb_byte *) xmalloc (len * width);
bufptr = *buffer;
- old_chain = make_cleanup (xfree, *buffer);
nfetch = partial_memory_read (addr, bufptr, len * width, &errcode)
/ width;
@@ -1243,8 +1253,6 @@
{
unsigned long bufsize = 0;
- *buffer = NULL;
-
do
{
QUIT;
@@ -1253,13 +1261,9 @@
if (*buffer == NULL)
*buffer = (gdb_byte *) xmalloc (nfetch * width);
else
- {
- discard_cleanups (old_chain);
- *buffer = (gdb_byte *) xrealloc (*buffer,
- (nfetch + bufsize) * width);
- }
+ *buffer = (gdb_byte *) xrealloc (*buffer,
+ (nfetch + bufsize) * width);
- old_chain = make_cleanup (xfree, *buffer);
bufptr = *buffer + bufsize * width;
bufsize += nfetch;
next reply other threads:[~2009-02-27 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 19:41 Phil Muldoon [this message]
2009-02-27 19:56 ` Tom Tromey
2009-02-27 22:11 ` Phil Muldoon
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=49A82F5C.9000801@redhat.com \
--to=pmuldoon@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