All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] fc_sort: memory leakages (was: Pull Request for fixing memory leak warning)
Date: Fri, 29 Sep 2017 20:43:46 +0200	[thread overview]
Message-ID: <1506710626.25420.2.camel@trentalancia.com> (raw)
In-Reply-To: <CAFftDdpSGRtE8wc4eTy66EPN3PAm9oE=aLCB_P0NvH4kHCH+1w@mail.gmail.com>

On Fri, 29/09/2017 at 09.30 -0700, William Roberts wrote:
> On Fri, Sep 29, 2017 at 9:52 AM, Guido Trentalancia via refpolicy
> <refpolicy@oss.tresys.com> wrote:
> > On Thu, 28/09/2017 at 15.24 -0700, William Roberts wrote:
> > > On Thu, Sep 28, 2017 at 5:12 PM, Guido Trentalancia via refpolicy
> > > <refpolicy@oss.tresys.com> wrote:

[...]

> > > So hopefully they can try it and let us know if it avoids the
> > > errors
> > > with their analysis tools,
> > > if valgrind reports 0 leaks, it likely will satisfy the static
> > > analysis.
> > 
> > The patch that I attached does not work properly and it needs
> > further
> > work, because it leads to a failure in getline() and an empty
> > output
> > file.
> > 
> > I hope it helps.
> 
> That's not very helpful IMHO, but thanks anyways. They took the PR
> upstream, so that should fix there static analysis issue and avoid
> any
> forking.

Yes, I know it's not particularly helpful. I have posted mainly because
the previous one was broken.

At the moment, I don't have time to look at it any further. Also, I do
not use the same analyzer that you have used, so I cannot reproduce the
same problem.

Regards,

Guido

  reply	other threads:[~2017-09-29 18:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 16:05 [refpolicy] Pull Request for fixing memory leak warning William Roberts
2017-09-29  0:12 ` [refpolicy] [PATCH] fc_sort: memory leakages (was: Pull Request for fixing memory leak warning) Guido Trentalancia
2017-09-28 22:24   ` William Roberts
2017-09-29 16:52     ` Guido Trentalancia
2017-09-29 16:30       ` William Roberts
2017-09-29 18:43         ` Guido Trentalancia [this message]
2017-09-29 17:37           ` William Roberts
2017-09-29 23:29         ` Guido Trentalancia
2017-09-29 18:35       ` [refpolicy] [PATCH v2] fc_sort: memory leakages Guido Trentalancia
2017-09-29 23:30         ` [refpolicy] [PATCH v3] " Guido Trentalancia
2017-09-30  6:03           ` [refpolicy] [PATCH v4] " Guido Trentalancia
2017-09-30 19:15             ` Guido Trentalancia
2017-09-30 22:44               ` [refpolicy] [PATCH v5] " Guido Trentalancia
2017-10-03  1:21                 ` Chris PeBenito
2017-10-04  9:41                   ` Guido Trentalancia
2017-10-04 18:05                     ` William Roberts
2017-10-04 20:59                       ` Guido Trentalancia
2017-10-04 21:02                 ` [refpolicy] [PATCH v6] " Guido Trentalancia
2017-10-04 23:31                   ` Chris PeBenito

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=1506710626.25420.2.camel@trentalancia.com \
    --to=guido@trentalancia.com \
    --cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.