From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] memory leaks in libmp
Date: Wed, 18 Jan 2017 02:23:05 +0100 [thread overview]
Message-ID: <CAHL7psHyDoQH3cv8xcE17BrTz=UnW_UbPATK0pN30L5FdpU5VA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
Hi, these other two defects identified from Coverity scan that you might
find interesting:
https://github.com/JehanneOS/jehanne/issues/5
https://github.com/JehanneOS/jehanne/issues/6
NOTE: 9front's guys consider these a false positive, since both
mptole(n, nil, 0, nil);
and
mptobe(n, nil, 0, nil);
are stupid bugs in the caller.
Since, I do stupid errors often, I prefer to fix the leak.
Still a lot of coverity defects are actually false positives.
I try to signal here only the actual bugs but I might be wrong, thus let me
know if you find these report useless and I will stop to annoy the list.
Giacomo
[-- Attachment #2: Type: text/html, Size: 955 bytes --]
next reply other threads:[~2017-01-18 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:23 Giacomo Tesio [this message]
2017-01-18 2:31 ` cinap_lenrek
2017-01-18 9:24 ` Giacomo Tesio
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='CAHL7psHyDoQH3cv8xcE17BrTz=UnW_UbPATK0pN30L5FdpU5VA@mail.gmail.com' \
--to=giacomo@tesio.it \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).