1. wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by euphoric (admin) Jul 19, 2018
- 1789 views
Greg,
When I use the alpha-4 DLLs, it can't get past the wxeu include file. It just quits with no error message.
If I run it interpreted, no problem!
If I use the prior DLLs, no problem.
Not sure why or exactly where inside it's failing. Anything that would help me pinpoint that?
2. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by ghaberek (admin) Jul 19, 2018
- 1784 views
Anything that would help me pinpoint that?
My first thought is that maybe you built a 64-bit executable and those DLLs are 32-bit.
Failing that, you can try getting a trace with GDB. That might help pinpoint where it's crashing.
- Open a Command Prompt and run gdb.
- Type run yourfile.exe
- Wait for the app to crash. GDB should display an exception.
- Type bt to print a backtrace.
- Type quit and Y to kill the application.
- Post the entire output in your reply.
You might need to add the -debug flag to your euc call in order get get debug info out of the executable.
In the mean time, I will see if I can reproduce the problem as soon as I can get to it.
-Greg
3. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by euphoric (admin) Jul 19, 2018
- 1780 views
- Open a Command Prompt and run gdb.
- Type run yourfile.exe
At this point, gdb says:
(gdb) run "HTF Software Manager.exe" Starting program: "HTF Software Manager.exe" No executable specified, use `target exec'.
4. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by ghaberek (admin) Jul 19, 2018
- 1758 views
At this point, gdb says:
(gdb) run "HTF Software Manager.exe" Starting program: "HTF Software Manager.exe" No executable specified, use `target exec'.
Sorry, got the steps wrong. That's what I get from writing it from memory.
- Type gdp executable
- Type run parameters-youd-normally-pass-on-the-command-line
- **CRASH**
- Type bt to show backtrace
This still might not result in a proper backtrace if there are no debugging symbols present.
-Greg
5. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by euphoric (admin) Jul 19, 2018
- 1756 views
I added -debug to the euc builder. Then did the gdb commands as you suggested, and here's the output:
C:\Users\FOADDEV\Programs\wxformsmanager\wxFormsManager>gdb "HTF Software Manage r.exe" GNU gdb (GDB) 7.9.1 Copyright (C) 2015 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 "x86_64-w64-mingw32". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from HTF Software Manager.exe...done. (gdb) run Starting program: C:\Users\FOADDEV\Programs\wxformsmanager\wxFormsManager\HTF So ftware Manager.exe [New Thread 4148.0xe78] warning: `C:\Windows\SYSTEM32\ntdll.dll': Shared library architecture i386:x86-6 4 is not compatible with target architecture i386. warning: `C:\Windows\SYSTEM32\wow64.dll': Shared library architecture i386:x86-6 4 is not compatible with target architecture i386. warning: `C:\Windows\system32\wow64win.dll': Shared library architecture i386:x8 6-64 is not compatible with target architecture i386. warning: `C:\Windows\system32\wow64cpu.dll': Shared library architecture i386:x8 6-64 is not compatible with target architecture i386. warning: Could not load shared library symbols for WOW64_IMAGE_SECTION. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for WOW64_IMAGE_SECTION. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for NOT_AN_IMAGE. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for NOT_AN_IMAGE. Do you need "set solib-search-path" or "set sysroot"? Program received signal SIGSEGV, Segmentation fault. 0x0000002b in ?? () (gdb) bt #0 0x0000002b in ?? () #1 0x00000000 in ?? ()
My euc version:
C:\Users\FOADDEV\Programs\wxformsmanager\wxFormsManager>euc -v Euphoria to C Translator v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2015-02-02 14:18:53, Id: 6300:57179171dbed
6. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by ghaberek (admin) Jul 19, 2018
- 1792 views
Euphoria to C Translator v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2015-02-02 14:18:53, Id: 6300:57179171dbed
I did some testing I'm not having a problem. It looks like we're using slightly different versions of 4.1.0 from 2015.
Euphoria to C Translator v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2015-02-13 18:10:12, Id: 6318:1c30095180a0
I must have got mine from a eubins release. I will see if I can dig it out. (Those are currently buried as a result of our recent server migration.)
Edit: Here you go: https://www.dropbox.com/s/7d9uvseuxzvifty/eubin-2015-05-20-1c30095180a0.zip?dl=1
-Greg
7. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by jmduro Oct 15, 2018
- 1634 views
I did some testing I'm not having a problem. It looks like we're using slightly different versions of 4.1.0 from 2015.
Euphoria to C Translator v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2015-02-13 18:10:12, Id: 6318:1c30095180a0
I must have got mine from a eubins release. I will see if I can dig it out. (Those are currently buried as a result of our recent server migration.)
Edit: Here you go: https://www.dropbox.com/s/7d9uvseuxzvifty/eubin-2015-05-20-1c30095180a0.zip?dl=1
-Greg
I noticed something similar with OE4 version of the libxlsxwriter wrapper. It only works with release 6318:1c30095180a0 on Windows 7 or 10 (32-bit), not with the one downloaded from OpenEuphoria.org. Linux version of the wrapper works with all releases of OE4.
Jean-Marc
8. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by jmduro Oct 15, 2018
- 1586 views
It's not that easy. Even if I copy the whole euphoria 4 32-bit folder from the working PC on the non-working PC, I can't get the libxlsxwriter wrapper to operate correctly on the non-working PC. It is too complicated for me.
9. Re: wxEuphoria: Running Compiled with Alpha-4 DLLs Results in App Quit
- Posted by jmduro Oct 15, 2018
- 1585 views
I finally found the problem: zlib1.dll has to be in the library path. On the working PC, it was provided by CodeTyphon which was only on the working PC!
I just had to copy zlib1.dll int the lib/test folder to get it work anywhere. Win32lib (I guess) answered "function xxx not found" which was not really exact.
Jean-Marc