Building current MMEX svn on Windows with MinGW gcc ?

[agb2008]

I am getting quite strange problem with current svn versions of mmex while
trying to compile them on Windows 7 using MinGW gcc...
Previously that method was working - but I haven't been using it for some time
(was using MS Visual Studio 2008) - but now I am trying to check current revision on
workstation where Visual Studio not installed and ... I manage to compile mmex
without errors, but can't run it When I execute it - it's just close without any
windows display. And without any errors... Do not understand what is happening.

Tested with 2 configurations:

1. gcc 4.6.2, wxWidgets 2.8.12 and boost 1.50.0
2. gcc 4.7.2, wxWidgets 2.9.4 and boost 1.53.0

Same result. svn 3481 and 3482.

Any suggestions what might be wrong ? All required libs present...

[Nikolay]

Please try svn 3484
But not shure if MinGW working but MS Visual c++ 2010 OK.

[agb2008]

I would like to reopen this thread - run a number of tests wit current SVN version of mmex
and current version of MinGW32 on Windows 7 platform. It's possible to build mmex.exe
but when ony tries to execute it - it's just exit (doing absolutely nothing: no windows creation,
no error messages...) Could anyone advice or help how to resolve this issue ? I know that
MS Visual Studio would work - but would like to use MinGW32 g++ compiler.

[Nikolay]

Hi Alexey,

Could you please build mmex with gcc in Debug mode.
In that case you will have some outputs into console (cmd).
And I can add more debug messages.

--Nikolay

[agb2008]

Hello Nikolay,
All that I've got from MinGW gdb:

G:\Tools\src\4829\build\msw>gdb mmex.exe
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from G:\Tools\src\4829\build\msw\mmex.exe...done.
(gdb) run
Starting program: G:\Tools\src\4829\build\msw\mmex.exe
[New Thread 5924.0x3a8]
[Inferior 1 (process 5924) exited normally]
(gdb)

I would not say that it's very informative - but that's all that I've got. If I try to start mmex.exe
from console window - all that I've got is return to command prompt immediately after execution...

[agb2008]

And more detailed manual step by step debug log:

Code: Select all

C:\opt\mmex\bin>gdb mmex.exe
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from C:\opt\mmex\bin\mmex.exe...done.
(gdb) b main
Breakpoint 1 at 0x62ec26: file ../../lib/lua/src/lua.c, line 482.
(gdb) r
Starting program: C:\opt\mmex\bin\mmex.exe
[New Thread 2772.0x13b8]

Breakpoint 1, main (argc=1, argv=0xa3530b8) at ../../lib/lua/src/lua.c:482
482       lua_State *L = luaL_newstate();  /* create state */
(gdb) next
483       if (L == NULL) {
(gdb) next
488       lua_pushcfunction(L, &pmain);
(gdb) next
489       lua_pushinteger(L, argc);  /* 1st argument */
(gdb) next
490       lua_pushlightuserdata(L, argv); /* 2nd argument */
(gdb) next
491       status = lua_pcall(L, 2, 1, 0);
(gdb) next
492       result = lua_toboolean(L, -1);  /* get result */
(gdb) next
493       finalreport(L, status);
(gdb) next
494       lua_close(L);
(gdb) next
495       return (result && status == LUA_OK) ? EXIT_SUCCESS : EXIT_FAILURE;
(gdb) next
496     }
(gdb) next
0x004010fd in __mingw_CRTStartup ()
(gdb) next
Single stepping until exit from function __mingw_CRTStartup,
which has no line number information.
0x00922bfc in ExitProcess@4 ()
(gdb) next
Single stepping until exit from function ExitProcess@4,
which has no line number information.
0x750679f8 in KERNEL32!BasepFreeActivationContextActivationBlock ()
   from C:\Windows\syswow64\kernel32.dll
(gdb) next
Single stepping until exit from function KERNEL32!BasepFreeActivationContextActi
vationBlock,
which has no line number information.
0x770dd4e0 in ntdll!TpSetPoolStackInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!TpSetPoolStackInformation,
which has no line number information.
0x770dd6d9 in ntdll!LdrVerifyImageMatchesChecksum ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrVerifyImageMatchesChecksum,
which has no line number information.
0x770bdf40 in ntdll!LdrWx86FormatVirtualImage ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrWx86FormatVirtualImage,
which has no line number information.
0x770dd723 in ntdll!LdrVerifyImageMatchesChecksum ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrVerifyImageMatchesChecksum,
which has no line number information.
0x770be134 in ntdll!LdrWx86FormatVirtualImage ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrWx86FormatVirtualImage,
which has no line number information.
0x770dd75f in ntdll!LdrVerifyImageMatchesChecksum ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrVerifyImageMatchesChecksum,
which has no line number information.
0x770dd4ef in ntdll!TpSetPoolStackInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!TpSetPoolStackInformation,
which has no line number information.
0x770b22a0 in ntdll!LdrQueryProcessModuleInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrQueryProcessModuleInformation,

which has no line number information.
0x770dd4fa in ntdll!TpSetPoolStackInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!TpSetPoolStackInformation,
which has no line number information.
0x770b22a0 in ntdll!LdrQueryProcessModuleInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrQueryProcessModuleInformation,

which has no line number information.
0x770dd505 in ntdll!TpSetPoolStackInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!TpSetPoolStackInformation,
which has no line number information.
0x770c816c in ntdll!RtlInitializeContext () from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!RtlInitializeContext,
which has no line number information.
0x770b22a0 in ntdll!LdrQueryProcessModuleInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!LdrQueryProcessModuleInformation,

which has no line number information.
0x770c81a5 in ntdll!RtlInitializeContext () from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!RtlInitializeContext,
which has no line number information.
0x770dd516 in ntdll!TpSetPoolStackInformation ()
   from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!TpSetPoolStackInformation,
which has no line number information.
0x770afc90 in ntdll!isdigit () from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!isdigit,
which has no line number information.
0x770afc9b in ntdll!RtlFindSetBits () from C:\Windows\system32\ntdll.dll
(gdb) next
Single stepping until exit from function ntdll!RtlFindSetBits,
which has no line number information.
0x74502320 in ?? ()
(gdb) next
Cannot find bounds of current function