From: Michael Snyder <msnyder@vmware.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfa] add_symbol_file_command, avoid memory leak.
Date: Sun, 27 Feb 2011 22:00:00 -0000 [thread overview]
Message-ID: <4D6AC8B5.4030702@vmware.com> (raw)
In-Reply-To: <20110227204206.GA11932@host1.dyn.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Jan Kratochvil wrote:
> On Sun, 27 Feb 2011 21:35:46 +0100, Michael Snyder wrote:
>> Jan Kratochvil wrote:
>>> While a nitpick it is a regression, that dont_repeat should be called even
>>> in the case of that error.
>> No, it's a fix. I moved the error before dont_repeat.
>
> Why? The manual says:
> `add-symbol-file' does not repeat if you press <RET> after using it.
> Other part of the manual says:
> and you can repeat certain GDB commands by typing just <RET>.
>
> There is nothing said that whether the command is / is not repated depends on
> its entered arguments.
>
> (Not sure if it matters to continue the discussion, I do not mind either way.)
Ah, sorry, I misunderstood you. I'm with you now.
How about this?
[-- Attachment #2: symfile2.txt --]
[-- Type: text/plain, Size: 968 bytes --]
2011-02-26 Michael Snyder <msnyder@vmware.com>
* symfile.c (add_symbol_file_command): Avoid memory leak.
Index: symfile.c
===================================================================
RCS file: /cvs/src/src/gdb/symfile.c,v
retrieving revision 1.307
diff -u -p -u -p -r1.307 symfile.c
--- symfile.c 26 Feb 2011 02:07:09 -0000 1.307
+++ symfile.c 27 Feb 2011 21:56:20 -0000
@@ -2169,15 +2169,15 @@ add_symbol_file_command (char *args, int
size_t num_sect_opts = 0;
struct cleanup *my_cleanups = make_cleanup (null_cleanup, NULL);
- num_sect_opts = 16;
- sect_opts = (struct sect_opt *) xmalloc (num_sect_opts
- * sizeof (struct sect_opt));
-
dont_repeat ();
if (args == NULL)
error (_("add-symbol-file takes a file name and an address"));
+ num_sect_opts = 16;
+ sect_opts = (struct sect_opt *) xmalloc (num_sect_opts
+ * sizeof (struct sect_opt));
+
argv = gdb_buildargv (args);
make_cleanup_freeargv (argv);
next prev parent reply other threads:[~2011-02-27 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 1:56 Michael Snyder
2011-02-27 20:35 ` Jan Kratochvil
2011-02-27 20:42 ` Michael Snyder
2011-02-27 20:51 ` Jan Kratochvil
2011-02-27 22:00 ` Michael Snyder [this message]
2011-02-27 22:12 ` Jan Kratochvil
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=4D6AC8B5.4030702@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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