[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Crash report for [mob:3054a76]

From: Michael Matz
Subject: Re: [Tinycc-devel] Crash report for [mob:3054a76]
Date: Wed, 9 Nov 2016 15:56:46 +0100 (CET)
User-agent: Alpine 2.20 (LSU 67 2015-01-07)


On Tue, 8 Nov 2016, Steffen Nurpmeso wrote:

> (gdb) run
> Starting program: 
> /home/steffen/usr-wales-arch-linux-x86_64/opt/tcc-mob/bin/tcc 
> -Wl,-rpath=/home/steffen/usr/lib -Wl,-rpath=/home/steffen/usr/opt/tcc-mob/lib 
> -Wl,-rpath=/home/steffen/usr/opt/pcc/lib -Wl,-rpath=/lib 
> -Wl,-rpath=/usr/local/lib -Wl,-rpath=/usr/lib -o s-nail-bmta bmta.o 
> -L/home/steffen/usr/lib -L/home/steffen/usr/opt/tcc-mob/lib 
> -L/home/steffen/usr/opt/pcc/lib -L/lib -L/usr/local/lib -L/usr/lib
> *** Error in `/home/steffen/usr-wales-arch-linux-x86_64/opt/tcc-mob/bin/tcc': 
> corrupted double-linked list: 0x000000000065c0f0 ***

Something in tcc is probably overwriting random memory which happens to be 
meta info malloc is using for its own implementation leading to the 
ovserved abort (which basically is a consistency check on that internal 
data).  valgrind often helps in identifying the real cause, so do:

$ valgrind ... tcc command line ...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]