zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH (differently) Re: PATCH: Plug some fd leaks in bin_print
Date: Wed, 07 Jan 2015 09:04:16 -0800	[thread overview]
Message-ID: <150107090416.ZM26931@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3TTRTnXG5HWcFOyzxADA=hm=juTwkrCGiKGH-XMRZdEzg@mail.gmail.com>

On Jan 7,  9:26am, Mikael Magnusson wrote:
} Subject: Re: PATCH (differently) Re: PATCH: Plug some fd leaks in bin_prin
}
} On Wed, Jan 7, 2015 at 8:14 AM, Bart Schaefer <schaefer@brasslantern.com> wrote:
} > On Jan 6, 11:08pm, Bart Schaefer wrote:
} > }
} > } Does coverity still find leaks after this?  What I've done is to move
} > } option validity checking earlier in the function so that fout should
} > } never get opened in the first place if we're not going to make proper
} > } use of it later.
} 
} Only Clint and Oliver have admin access, so I can't actually upload
} new code to coverity to check. Maybe if either of them see this they
} could add me/us as admins too?

I can push this to the master git a bit later today if nobody sees any
obvious problems with it.  "make check" does still pass.

You can see from that one hunk that the precedence of options is a bit
wacky.  -c / -C win if there is no format string but -z / -s win if
there is one.  I guess that sort of makes sense because columnation of
formatted output isn't supported.


  reply	other threads:[~2015-01-07 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07  0:25 Mikael Magnusson
2015-01-07  1:21 ` Bart Schaefer
2015-01-07  3:15   ` Mikael Magnusson
2015-01-07  6:35 ` Bart Schaefer
2015-01-07  7:08   ` PATCH (differently) " Bart Schaefer
2015-01-07  7:14     ` Bart Schaefer
2015-01-07  8:26       ` Mikael Magnusson
2015-01-07 17:04         ` Bart Schaefer [this message]
2015-01-07  8:04   ` Mikael Magnusson
2015-01-07  8:06     ` Mikael Magnusson

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=150107090416.ZM26931@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).