Date: Sun, 19 Feb 2006 09:32:56 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: freebsd-current@freebsd.org Subject: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late) Message-ID: <43F8ABC8.30005@FreeBSD.org> In-Reply-To: <20060219110732.GA12550@stud.fit.vutbr.cz> References: <1140187193.731.47.camel@spirit> <20060217181842.GA21033@odin.ac.hmc.edu> <43F65A70.7080608@FreeBSD.org> <20060217234118.GA22643@odin.ac.hmc.edu> <43F67121.5080809@FreeBSD.org> <43F682F2.1020804@FreeBSD.org> <43F68611.7080602@FreeBSD.org> <20060219110732.GA12550@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Divacky Roman wrote:
> I tried running rcorder under valgrind and it showed me massive
> leaks/double-frees etc. unfortunately I am not able to run valgrind on recent
> 7-current (when I start it it just creates 2.8G coredump)
>
> it would be great to run coverity on rcorder or something to reveal the bugs. I
> am willing to hack on it but I'd appreciate some help (either the valgrind
> running or list of coverity revealed bugs)
I actually requested a coverity check of the code, and it didn't turn up
anything. The code for rcorder is the same in both HEAD and RELENG_6,
although obviously you won't get the new malloc if you are running in the
latter. However, I'm guessing that if you fix things that are obviously bugs
that are exposed by valgrind on RELENG_6, it would still be valuable to
bring those fixes into HEAD first.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43F8ABC8.30005>