Hi, 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 ... Ciao, Michael. _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
