Thank you for all your help. I have succeeded in resolving the issue. As I
stated in my first email, I am using gcc to compile tcc. gcc is indeed
putting underscores at the beginning of symbol names and is using the PE
object file format. To work around this, I patched the tcc4tcl build
process to
Dear all,
While fuzzing tcc, an out of bounds write was found in the end_macro
function.
Attached are a file producing a crash when compiled and the output of
valgrind.
To reproduce, compile the attached input file with tcc
tcc end_macro.c
The latest git version of tcc (commit
Hi,
On Tue, 12 Mar 2019, Andy Goth wrote:
> So there's the big clue. The code is asking for ashldi3 with two leading
> underscores, but the archive index contains ashldi3 with three leading
> underscores. Thus, the archive object libtcc1.o doesn't contain the
> requested symbol and therefore is
Hi Andy,
I stepped into my code and followed the same path as you to where __divdi3 etc.
is searched, but in my case it is found because libtcc1-32.a (which I got here:
http://download.savannah.gnu.org/releases/tinycc/tcc-0.9.27-win32-bin.zip)
contains the version with 2 underscores:
