On Sat, Mar 31, 2012 at 6:58 PM, Vincent Torri wrote:
> Hey
>
> I'm writing a small tool to do mem leak check, and later GDI leak
> checks. That tool, named 'examine', is intended to be used like
> valgrind, that is, no linkage (unlike mpatrol, for example). The usage
> is : examine my_test_app.e
Hey
I'm writing a small tool to do mem leak check, and later GDI leak
checks. That tool, named 'examine', is intended to be used like
valgrind, that is, no linkage (unlike mpatrol, for example). The usage
is : examine my_test_app.exe
I've beginning to write it for several reasons. First : improv
Op 31 mrt. 2012 18:25 schreef "Andreas Schmidt" het
volgende:
>
> Hi all,
>
> I tried compiling my stuff with rubenvb's
> "x86_64-w64-mingw32-gcc-4.6.4_rubenvb.7z"
> and I got the following linking error:
>
> g++ -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import
> -Wl,-enable-runtime-pseudo-reloc
Hi,
__C_specific_handler function is an export of msvcrt. Therefore it
means that you either are linking multiple-times msvcrt-runtime DLLs,
or one of your own DLL-files is also exporting '__C_specific_handler'
as symbol.
Easiest attempt to fix this is by keeping order of objects and
libaries as
Hi all,
I tried compiling my stuff with rubenvb's
"x86_64-w64-mingw32-gcc-4.6.4_rubenvb.7z"
and I got the following linking error:
g++ -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import
-Wl,-enable-runtime-pseudo-reloc -Wl,-s -mthreads -Wl,-subsystem,windows
-o release\Qt_test5.exe object_scri
