Date: Sun, 19 Feb 2006 12:07:32 +0100 From: Divacky Roman <xdivac02@stud.fit.vutbr.cz> To: freebsd-current@freebsd.org Subject: Re: New RCorder: abi loaded too late Message-ID: <20060219110732.GA12550@stud.fit.vutbr.cz> In-Reply-To: <43F68611.7080602@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 17, 2006 at 06:27:29PM -0800, Jason Evans wrote: > Doug Barton wrote: > >PS to jasone, the trace on the core file shows that the error in rcorder is > >at line 761 of rcorder.c (which was recently patched to fix a different > >kind > >of core dumping problem). I'd be glad to provide you or the list with more > >details if there is interest. > > Chances are good that the crash is due to a double free. If you have > trouble tracking this down, you can try reducing the size of the delay > cache (MALLOC_OPTIONS='cccccccc' will reduce the delay cache to one > item), which may cause a different failure mode that is easier to interpret. 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) roman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060219110732.GA12550>