Date: Fri, 6 Nov 2009 13:33:05 -0600 From: Peter Steele <psteele@maxiscale.com> To: "usleepless@gmail.com" <usleepless@gmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: RE: system() call causes core dump Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3394EED3@MBX03.exg5.exghost.com> In-Reply-To: <c39ec84c0911060931p48de1ae6s2aedfa24d5c0e210@mail.gmail.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB327D117F@MBX03.exg5.exghost.com> <4AEC5E02.8040705@FreeBSD.org> <7B9397B189EB6E46A5EE7B4C8A4BB7CB327D11A9@MBX03.exg5.exghost.com> <200911040149.48701.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <7B9397B189EB6E46A5EE7B4C8A4BB7CB3394ED41@MBX03.exg5.exghost.com> <c39ec84c0911060743sce9de02n5acb19663cf880df@mail.gmail.com> <7B9397B189EB6E46A5EE7B4C8A4BB7CB3394EDDF@MBX03.exg5.exghost.com> <c39ec84c0911060931p48de1ae6s2aedfa24d5c0e210@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think the crash in the malloc is from a malloc in fstat or grep ( there is no malloc in system() ). As a test I changed the 'fstat|wc -l' call we use now to 'ps aux|wc -l'. The problem does not occur all the time but the QA group is seeing it periodically during their test runs. I'm going to let the alternative version got through some days of testing to see if the problem occurs again. If it doesn't, it may very well be something to do with fstat. If it does, well, I guess we have more digging to do...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B9397B189EB6E46A5EE7B4C8A4BB7CB3394EED3>