Re: directory y: exe runs properly, directory x: exe quits straightaway

[Marco Atzeri <marco.atzeri@gmail.com>]

On 14/02/2014 18:44, lothar atheling wrote:
>
> i am porting an application built with Visual C++ to build under Mingw
> gcc (CXX=/usr/bin/i686-w64-mingw32-g++)

this is not the mingw list...

> in my development directory x, the program apparently builds correctly,
> but it quits directly when run.
>
> when i copy the exe to another directory y, the program runs well.
>
> also, in the development directory, ldd shows:
> $ ldd mung.exe
>          ntdll.dll => /xp0/WINDOWS/system32/ntdll.dll (0x7c900000)
>          kernel32.dll => /xp0/WINDOWS/system32/kernel32.dll (0x7c800000)
>
> while in the copy directory, ldd shows:
> $ ldd mung.exe
>          ntdll.dll => /xp0/WINDOWS/system32/ntdll.dll (0x7c900000)
[cut]
>          glut32.dll => /usr/bin/glut32.dll (0x10000000)
>          WINMM.dll => /xp0/WINDOWS/system32/WINMM.dll (0x76b40000)
>          libgcc_s_sjlj-1.dll =>
>          /usr/i686-w64-mingw32/sys-root/mingw/bin/libgcc_s_sjlj-1.dll
>          (0x6cec0000)
>          libstdc++-6.dll =>
>          /usr/i686-w64-mingw32/sys-root/mingw/bin/libstdc++-6.dll
>          (0x6fc40000)
>
> this behaviour has some reproducibility: if i copy the development
> directory with tar and rebuild, the behaviour represents, whereas if i
> make a new build directory, copy the sources and the makefile and
> rebuild, the behaviour vanishes.

ldd is not the right tool for this search.
It does not show the DLLs not available on path

try:
objdump -x mung |grep "DLL Name"




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple