Thanks for the help !

Testing on my linux X86_64 give me this error:

-----
~/dev/c/tinycc/tests$ ../tcc -B.. -I.. -I.. -I../include
-DCONFIG_LDDIR="\"lib\"" -DCONFIG_MULTIARCHDIR="\"x86_64-linux-gnu\""
-DTCC_TARGET_X86_64 -DONE_SOURCE -o tcc.tcc ../tcc.c -ldl

~/dev/c/tinycc/tests$ valgrind --tool=memcheck ./tcc.tcc
==5044== Memcheck, a memory error detector
==5044== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5044== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==5044== Command: ./tcc.tcc
==5044==

valgrind: m_debuginfo/readelf.c:2352 (vgModuleLocal_read_elf_debug_info):
Assertion 'crc_offset + sizeof(UInt) <= debuglink_escn.szB' failed.
==5044==    at 0x3804F522: ??? (in
/home/mingo/local/lib/valgrind/memcheck-amd64-linux)

sched status:
  running_tid=0


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.


On Thu, Apr 3, 2014 at 5:07 PM, Michael Matz <matz....@frakked.de> wrote:

> Hi,
>
> On Wed, 2 Apr 2014, Domingo Alvarez Duarte wrote:
>
> > 1- "Inconsistency detected by ld.so: rtld.c: 1292: dl_main: Assertion
> > `_rtld_local._dl_rtld_map.l_libname' failed!" for this one I found a
> > workaround making a change on tccelf.c (it's on the mob but commented
> > because it has a side effect of programs generated with debug information
> > and stripped afterwards segfaults).
>
> I think I've fixed this one.  TCC was emitting ELF files that aren't liked
> by binutils strip, and creating a PT_PHDR exposed those problems.  mob
> since f2c8491 should work (at least valgrind before and after stripping
> executables for x86 and x86-64 do).
>
>
> Ciao,
> Michael.
>
> _______________________________________________
> Tinycc-devel mailing list
> Tinycc-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to