Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: msnyder@sonic.net
To: gdb-patches@sourceware.org
Subject: [PATCH] stack.c, memory leak (no-effect code?)
Date: Fri, 10 Aug 2007 22:19:00 -0000	[thread overview]
Message-ID: <5638.12.7.175.2.1186784359.squirrel@webmail.sonic.net> (raw)

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

This patch is to fix a memory leak, but while you're looking at it...
does it seem to you that these two blocks have any effect?

[Sorry if I posted this before, I've been searching for it...]


[-- Attachment #2: 160.txt --]
[-- Type: text/plain, Size: 926 bytes --]

2007-08-04  Michael Snyder  <msnyder@access-company.com>

	* stack.c (print_frame): Memory leak.

Index: stack.c
===================================================================
RCS file: /cvs/src/src/gdb/stack.c,v
retrieving revision 1.150
diff -p -r1.150 stack.c
*** stack.c	25 Jul 2007 00:28:25 -0000	1.150
--- stack.c	5 Aug 2007 02:16:10 -0000
*************** print_frame (struct frame_info *frame, i
*** 582,587 ****
--- 582,589 ----
  		   the symbol table. That'll have parameters, but
  		   that's preferable to displaying a mangled name.  */
  		funname = SYMBOL_PRINT_NAME (func);
+ 	      else
+ 		xfree (demangled);
  	    }
  	}
      }
*************** frame_info (char *addr_exp, int from_tty
*** 882,887 ****
--- 884,891 ----
  	     preferable to displaying a mangled name.  */
  	  if (demangled == NULL)
  	    funname = SYMBOL_PRINT_NAME (func);
+ 	  else
+ 	    xfree (demangled);
  	}
      }
    else

             reply	other threads:[~2007-08-10 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 22:19 msnyder [this message]
2007-08-13 19:41 ` Jim Blandy
2007-08-13 22:27   ` msnyder
2007-08-18  0:20     ` msnyder

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=5638.12.7.175.2.1186784359.squirrel@webmail.sonic.net \
    --to=msnyder@sonic.net \
    --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