Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix fopen related cleanups
Date: Tue, 28 Oct 2008 16:25:00 -0000	[thread overview]
Message-ID: <20081028142000.GA22331@caradoc.them.org> (raw)
In-Reply-To: <m3od15pkz4.fsf@fleche.redhat.com>

On Mon, Oct 27, 2008 at 07:27:43PM -0600, Tom Tromey wrote:
> While looking into another issue, I noticed a number of fopen-related
> buglets in gdb.  In particular, there are several places in gdb where
> a file is not properly closed if an error occurs.
> 
> This patch fixes all the fopen-related problems.  It also fixes a
> couple memory leaks I noticed while writing this.  Finally, it
> consolidates all the implementations of make_cleanup_fclose, explicit
> or implicit, into a single place.
> 
> I think there are also some file-close-related flaws having to do with
> open (procfs_pidlist -- this function is flawed in a few ways) and
> also gdb_fopen (instances in dummy-frame.c, regcache.c, and
> reggroups.c according to my notes).  I haven't yet checked opendir,
> socket, or pipe.  I will deal with those in separate patches.
> 
> Built and regtested on x86-64 (compile farm).
> Of course, this does not show whether the bug is fixed or not.
> For that I relied on inspection.
> 
> Please review.

Looks OK to me.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2008-10-28 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28  2:04 Tom Tromey
2008-10-28 16:25 ` Daniel Jacobowitz [this message]

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=20081028142000.GA22331@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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