From: Pedro Alves <palves@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Fix leaks when pruning inferiors.
Date: Thu, 05 Dec 2019 16:42:00 -0000 [thread overview]
Message-ID: <fca2549c-0600-0cec-a0b3-c7c07e4cc842@redhat.com> (raw)
In-Reply-To: <20191201155220.15971-1-philippe.waroquiers@skynet.be>
On 12/1/19 3:52 PM, Philippe Waroquiers wrote:
> Origin of the leaks is in prune_inferiors: prune_inferiors is first removing
> the inferior to prune from the inferior list, then calls delete_inferior.
> But delete_inferior will only really destroy the inferior when it finds
> it into the inferior list.
> As delete_inferior is removing the inferior to delete from the inferior list,
> ensure prune_inferiors only calls delete_inferior, without touching the
> inferior list.
Whoops.
> @@ -370,24 +370,22 @@ have_live_inferiors (void)
> void
> prune_inferiors (void)
> {
> - struct inferior *ss, **ss_link;
> + struct inferior *ss, *ss_next;
>
>
> - *ss_link = ss->next;
> + ss_next = ss->next;
> delete_inferior (ss);
> - ss = *ss_link;
> + ss = ss_next;
Please declare ss_next here instead of at the top.
You can omit the redundant "struct" while at it:
inferior *next = ss->next;
delete_inferior (ss);
ss = next;
OK with that change. Thanks!
Pedro Alves
next prev parent reply other threads:[~2019-12-05 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 15:52 Philippe Waroquiers
2019-12-05 16:42 ` Pedro Alves [this message]
2019-12-05 22:30 ` Philippe Waroquiers
2019-12-05 16:44 ` Kevin Buettner
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=fca2549c-0600-0cec-a0b3-c7c07e4cc842@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).