[Top][All Lists]

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

Re: [Tinycc-devel] Problem with kernel32 in DLL

From: Luis Alejandro Muzzachiodi
Subject: Re: [Tinycc-devel] Problem with kernel32 in DLL
Date: Sat, 9 Oct 2010 12:42:16 -0700 (PDT)

Of course, i understand what complicate is for you guess what's wrong.
But having to limit the problem my presumption " a priori " it is that the problem is not in the code that is working well in Linux, Mac and Windows (the same code compiled with GCC and is also compiled ok with TCC). The problem (for me) is in/related the TCC' DLL :
1) Generating the DLL without " - rdynamic" tiny_impdef fails, and scripts (TCL) also fails (do not find libxyz_init).
2) With " - rdynamics" tiny_imdef generates def ok, scripts work ok but they lose the text in the windows
3) Comparing both DLL (GCC & TCC versions) according to "dependency walker" TCC's DLL lacking kernel32 in the first level, missing three functions (as mentioned in previous mail).
4) Comparing both .def, the DLL generated by GCC has the lines:
 .idata$4 .idata$5 .idata$6 _IMPORT_DESCRIPTOR_tcl85 _NULL_IMPORT_DESCRIPTOR that are not in the TCC version and  TCC's has
 address@hidden __ashldi3 __ashrdi3 __chkstk __divdi3 address@hidden __fini_array_end __fini_array_start __fixunsdfdi __fixunssfdi __fixunsxfdi __floatundidf __floatundisf __floatundixf __init_array_end __init_array_start __lshrdi3 __moddi3 __preinit_array_end __preinit_array_start __tcc_fpu_control __tcc_int_fpu_control __udivdi3 __umoddi3 _edata _end _etext
that are not in the generated by GCC.
The rest (functions of the library) is the same.

Something of this help you?. I hope ...

__ Alejandro ___

--- El vie 8-oct-10, grischka <address@hidden> escribió:

De: grischka <address@hidden>
Asunto: Re: [Tinycc-devel] Problem with kernel32 in DLL
Para: address@hidden
Fecha: viernes, 8 de octubre de 2010, 8:24

Luis Alejandro Muzzachiodi wrote:
> Very hard. There are more than 80 files chained among them and with GTK's/TCL's libraries(and i'm not the author).
> Sorry, i think that's easy send you .o files or .dll files for test.
> However, if you can be more specific about what are you looking for, may be i could ask for help the author.

Before we can look for a bug in TCC we need to know the bug in the
compiled program why it "does not show any text in the windows".
Obviously some information is lost somewhere somehow.  We need to
know what and where and how exactly.

--- grischka

reply via email to

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