Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 01/10] change gdb to refcount bfd everywhere
Date: Mon, 23 Jul 2012 14:52:00 -0000	[thread overview]
Message-ID: <87394isf77.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120723085355.GA29593@host2.jankratochvil.net> (Jan	Kratochvil's message of "Mon, 23 Jul 2012 10:53:55 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Tom> This changes allocate_objfile to acquire a reference to the BFD,
Tom> rather than steal a reference.  Then it changes all callers, direct or
Tom> indirect, to follow.

Jan> map_vmap still steals a reference.

I'll investigate.

One thing I noticed is that bfd_openr_next_archived_file doesn't
document who owns the resulting BFD.  Must one close it?  Or is it
closed when the parent BFD is closed?  I think the latter; or at least,
if not the latter then the caching mechanism in bfd/archive.c is badly
broken.  Anyway, whatever bugs exist here are latent ones already in gdb.

Tom> I'm still undecided as to whether this patch is an improvement.  I
Tom> think it does fix a couple of obscure latent memory leaks.

Jan> I find the code the only way "how it should be" now.

Ok.  I'm going to put those in.

Tom


  parent reply	other threads:[~2012-07-23 14:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 19:32 Tom Tromey
2012-07-19 14:18 ` Jan Kratochvil
2012-07-19 20:58   ` Tom Tromey
2012-07-20 16:37     ` Tom Tromey
2012-07-20 18:11       ` Jan Kratochvil
2012-07-20 16:37     ` Tom Tromey
2012-07-23  8:54       ` Jan Kratochvil
2012-07-23  9:06         ` Jan Kratochvil
2012-07-23 15:23           ` Tom Tromey
2012-07-23 15:25             ` Tom Tromey
2012-07-24 13:17             ` Jan Kratochvil
2012-07-24 19:52               ` Tom Tromey
2012-07-24 20:27                 ` Eli Zaretskii
2012-07-25 14:25                   ` Tom Tromey
2012-07-25 14:29                     ` Jan Kratochvil
2012-07-25 14:52                       ` Tom Tromey
2012-07-25 14:55                         ` Jan Kratochvil
2012-07-25 15:44                           ` Tom Tromey
2012-07-25 15:37                     ` Eli Zaretskii
2012-07-25 11:57                 ` Jan Kratochvil
2012-07-23 14:52         ` Tom Tromey [this message]
2012-07-23 18:54         ` Tom Tromey
2012-07-23 19:02           ` Jan Kratochvil
2012-07-23 19:08             ` Tom Tromey
2012-07-22 19:00     ` Jan Kratochvil
2012-07-23 14:49       ` Tom Tromey
2012-07-23 15:01         ` Tom Tromey
2012-07-23 15:03         ` Tom Tromey
2012-07-20 16:31   ` Tom Tromey
2012-07-20 18:10     ` 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=87394isf77.fsf@fleche.redhat.com \
    --to=tromey@redhat.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