From: Jason Molenda <jmolenda@apple.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/PING] Fix a small memory leak in bpstat_stop_status
Date: Mon, 10 Mar 2003 22:42:00 -0000 [thread overview]
Message-ID: <49B89DE7-5349-11D7-B4EE-003065BC3540@apple.com> (raw)
In-Reply-To: <20030310190348.GF967@gnat.com>
My agreement doesn't help you at all :-), but this patch looks correct
to me--we will leak a copy of the "silent" command in
bpstat_stop_status() without this patch.
Jason
On Monday, March 10, 2003, at 11:03 AM, Joel Brobecker wrote:
> Hello,
>
> Can somebody have a look at this patch please (2nd ping)? Granted, it
> is
> not a very important patch, it "only" fixes a small memory leak, but
> I believe the change is very localized, so easy to review.
>
> Thanks!
>
> On Thu, Dec 12, 2002 at 11:40:58AM +0100, Joel Brobecker wrote:
>> This is a followup on a thread that I started, archived at:
>> http://sources.redhat.com/ml/gdb-patches/2002-12/msg00358.html
>>
>> Basically, I extracted the part that fixed a small memory leak, and
>> tested it separately, as the other part of the patch is likely to be
>> superseeded by another patch submitted by Klee Dienes.
>>
>> 2002-12-12 Joel Brobecker <brobecker@gnat.com>
>>
>> * breakpoint.c (bpstat_stop_status): Fix a small memory leak.
>>
>> No regressions on x86-linux.
>>
>> Ok to apply?
>> --
>> Joel
>
>> Index: breakpoint.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/breakpoint.c,v
>> retrieving revision 1.100
>> diff -c -3 -p -r1.100 breakpoint.c
>> *** breakpoint.c 4 Dec 2002 04:53:13 -0000 1.100
>> --- breakpoint.c 12 Dec 2002 10:21:53 -0000
>> *************** bpstat_stop_status (CORE_ADDR *pc, int n
>> *** 2763,2771 ****
>> /* We will stop here */
>> if (b->disposition == disp_disable)
>> b->enable_state = bp_disabled;
>> - bs->commands = copy_command_lines (b->commands);
>> if (b->silent)
>> bs->print = 0;
>> if (bs->commands &&
>> (STREQ ("silent", bs->commands->line) ||
>> (xdb_commands && STREQ ("Q", bs->commands->line))))
>> --- 2767,2775 ----
>> /* We will stop here */
>> if (b->disposition == disp_disable)
>> b->enable_state = bp_disabled;
>> if (b->silent)
>> bs->print = 0;
>> + bs->commands = b->commands;
>> if (bs->commands &&
>> (STREQ ("silent", bs->commands->line) ||
>> (xdb_commands && STREQ ("Q", bs->commands->line))))
>> *************** bpstat_stop_status (CORE_ADDR *pc, int n
>> *** 2773,2778 ****
>> --- 2777,2783 ----
>> bs->commands = bs->commands->next;
>> bs->print = 0;
>> }
>> + bs->commands = copy_command_lines (bs->commands);
>> }
>> }
>> /* Print nothing for this entry if we dont stop or if we dont
>> print. */
>
>
> --
> Joel
>
next prev parent reply other threads:[~2003-03-10 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 2:48 [RFA] " Joel Brobecker
2003-01-13 3:22 ` Joel Brobecker
2003-03-10 19:04 ` [RFA/PING] " Joel Brobecker
2003-03-10 22:42 ` Jason Molenda [this message]
2003-03-10 23:10 ` Andrew Cagney
2003-03-11 19:07 ` Joel Brobecker
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=49B89DE7-5349-11D7-B4EE-003065BC3540@apple.com \
--to=jmolenda@apple.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.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