Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [rfa] add_symbol_file_command, avoid memory leak.
@ 2011-02-27  1:56 Michael Snyder
  2011-02-27 20:35 ` Jan Kratochvil
  0 siblings, 1 reply; 6+ messages in thread
From: Michael Snyder @ 2011-02-27  1:56 UTC (permalink / raw)
  To: gdb-patches

[-- Attachment #1: Type: text/plain, Size: 114 bytes --]

This looks straightforward, but I'd appreciate review.
I don't really understand why sect_opts never gets freed?


[-- Attachment #2: symfile.txt --]
[-- Type: text/plain, Size: 938 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 01:35:32 -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);
 
+  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));
 
   dont_repeat ();
 
-  if (args == NULL)
-    error (_("add-symbol-file takes a file name and an address"));
-
   argv = gdb_buildargv (args);
   make_cleanup_freeargv (argv);
 

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-02-27 22:05 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-27  1:56 [rfa] add_symbol_file_command, avoid memory leak 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
2011-02-27 22:12         ` Jan Kratochvil

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox