From mint-bounce@lists.fishpool.fi Wed Jan 27 08:48:36 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=5Ni4jEk6Z4lyjdRYI7iZvAvfdLOs+Rpjb042dKEDIz8=; b=NLFKyXxw9azOueu48cP8tUjbvgjKkG5eoLmAtO0J4oazpEzi0P3+JZjK+QmKVvsIUD 03C0YUTzUx2rMNYCSEC/EoDmBNLONN99+SSoAd1wyn969V+E83LwJFFjjL2Lj+vsPcw0 GezQTwp4LNeFlJUofQveDsgCa8J9VfCgKQUh4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=MOok/oSiQRzCps654IOvwmNdpY61avdIvm4E+GMssLlp1mis3WIP9jHdBkRd0U22nJ f5pGrE+mQ886r+2vBEo7tWAD/l+XapVgdarxpbxNqRUZJ/rqaFaa9W40raCbhJGdWVNR 9fHWheaOgnMAjp0g+beyv3AtKoFAuh6Y1x4hU= MIME-Version: 1.0 In-Reply-To: <4B5E068E.4020202@atari-source.org> References: <4B5E04D7.50708@atari-source.org> <4B5E068E.4020202@atari-source.org> Date: Wed, 27 Jan 2010 07:43:08 -0600 Message-ID: <11a6f2b11001270543j3d9c261bx380c05b5b66274f4@mail.gmail.com> Subject: Re: [MiNT] Malloc Bug From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0RDmVYx002033 On Mon, Jan 25, 2010 at 3:01 PM, Mark Duckworth wrote: > On 1/25/10 3:53 PM, Mark Duckworth wrote: >> >> Hey guys, >> >> More detail on the malloc bug.  I've been able to almost consistently >> reproduce it on my gcc 4.4.x/cvs mintlib aranym system.  The package that >> most consistently produces it is an rpm --rebuild of rcs.  It dies like >> this: >> >> /usr/include/ctype.h:76:1: warning: this is the location of the previous >> definition >> gcc  -g -O ident.o rcsmap.o version.o  -o ident >> gcc -c  -Dhas_conf_h  -I. -I. -g -O merge.c >> make: ../mintlib/malloc.c:187: __free: Assertion `s == r' failed. >> make: *** [install] Error 134 >> Bad exit status from /var/tmp/rpm-tmp.54754 (%install) >> root@arawork:/h/srpms> >> >> Importantly, it has done this before, and now it is doing this every time >> I try.  I'm assuming that if I reboot the problem will be gone.  If it's not >> then we're really talking.  But on this system I have done NOTHING more than >> start xaaes and do package builds so the problem lies within those >> facilities.  Next time I will not start xaaes. >> >> Thanks, >> Mark >> >> >> > Yeah it doesnt' do it after a fresh boot.  But what I will do is rebuild > make with debugging symbols, build a  bunch of packages and revisit it. >  Maybe I can examine the buffers and see what is in there.  Maybe something > will stand out. > > Thanks, > Mark > anything to try and get a consistant reproduction So I gather so far, you need something that splinters the memory in some way, to the point where an rpm --rebuild of rcs will consistantly fail. I suggest using zView on a large images folder, paired with FreeGEM 2 to quickly get the desired effect. You will need a large image folder tho. Hmm, ARAnyM with a "save state" might be useful here. If someone could produce the problem in STEem (or any emu with state saving) this might speed up the finding of a solution to this malloc issue.. Paul