1. eu4 2166 executable crash
- Posted by ChrisB (moderator) Jun 22, 2009
- 1267 views
Hi
Here's an interesting one.
On Linux.
Running the interpreter, a wxeu program, I get an error relating to a glibc detected realloc(), invalid next size 0x086981d0 , then a backtrace (lots of hex, some libraries). No ex.err produced.
Running the interpreter with other, smaller, wxeu programs, and they run fine.
Bind the program causing the crash, and then it runs fine.
Running with gdb args exu wxFaxMan.exu produced a Failed to read a valid object file image from memory, and malloc(): memory corruption(fast)
Note exu is simply eui renamed.
Any further info needed?
Chris
2. Re: eu4 2166 executable crash
- Posted by mattlewis (admin) Jun 22, 2009
- 1203 views
Running the interpreter, a wxeu program, I get an error relating to a glibc detected realloc(), invalid next size 0x086981d0 , then a backtrace (lots of hex, some libraries). No ex.err produced.
Note exu is simply eui renamed.
What version of eui and wxEuphoria are you running? There were some changes to the structure of sequences and atoms that are only reflected in the bleeding edge release of wxEuphoria.
Matt
3. Re: eu4 2166 executable crash
- Posted by ChrisB (moderator) Jun 22, 2009
- 1234 views
Hi
eu 2166, and wxeu pre change to wxeud.e (0.9 I think), so it is a slightly older one, but I could never get the newer one to work. (loads of not founds when running ldd on libwxeu.so.13).
Chris
4. Re: eu4 2166 executable crash
- Posted by mattlewis (admin) Jun 22, 2009
- 1239 views
Hi
eu 2166, and wxeu pre change to wxeud.e (0.9 I think), so it is a slightly older one, but I could never get the newer one to work. (loads of not founds when running ldd on libwxeu.so.13).
You're doomed to crashing with that setup. You want to get libwxeu.so.14 (that's the bleeding edge version). It's backwards compatible with eu 3.1, but the only binary version released that's compatible with a recent eu 4.0.
Are you running a 64 bit system? Another issue is that you may be running an ANSI build of wxWidgets. The released version of wxEuphoria expects a Unicode version. Building from source should make it all work. The configure script checks with your installed version of wxWidgets to make sure it gets all the compiler flags correct.
From memory, you'll need the headers for at least wxWidgets and GTK2+ installed in order to build from source.
Matt
5. Re: eu4 2166 executable crash
- Posted by ChrisB (moderator) Jun 22, 2009
- 1218 views
Hi
eu 2166, and wxeu pre change to wxeud.e (0.9 I think), so it is a slightly older one, but I could never get the newer one to work. (loads of not founds when running ldd on libwxeu.so.13).
You're doomed to crashing with that setup. You want to get libwxeu.so.14 (that's the bleeding edge version). It's backwards compatible with eu 3.1, but the only binary version released that's compatible with a recent eu 4.0.
Yes I do. Where from? I can only see vers 0.13, and the the 'go here' link points to itself 
Are you running a 64 bit system? Another issue is that you may be running an ANSI build of wxWidgets. The released version of wxEuphoria expects a Unicode version. Building from source should make it all work. The configure script checks with your installed version of wxWidgets to make sure it gets all the compiler flags correct.
Actually I run a 64 bit and a 32 bit system on the same network, so I have access to both, but I've invariably found compiling leads to chasing dependencies, which to be quite honest, I don't really want to spend my time doing.
This is one of my bugbears with Linux - installing new programs (and printer support). I'm and 'end user' more than a pioneer, and in a perfect world I would like to download, install a new program, put a few required libraries in /usr/lib, and just go. If the program wants a library, the install script should know where to get it from. 64 bits shouldn't matter. I don't care about unicode.
Sorry, ranting.
From memory, you'll need the headers for at least wxWidgets and GTK2+ installed in order to build from source.
Matt
See what I mean!
Thanks for your efforts Matt.
Chris
6. Re: eu4 2166 executable crash
- Posted by mattlewis (admin) Jun 22, 2009
- 1253 views
You're doomed to crashing with that setup. You want to get libwxeu.so.14 (that's the bleeding edge version). It's backwards compatible with eu 3.1, but the only binary version released that's compatible with a recent eu 4.0.
Yes I do. Where from? I can only see vers 0.13, and the the 'go here' link points to itself
v0.13 is the version of wxEuphoria that you need. The binary isn't synchronized, since it uses a single number, where the library itself goes a little further than that.
Here's the download page on sourceforge:
https://sourceforge.net/project/showfiles.php?group_id=73684&package_id=73795&release_id=689546
Are you running a 64 bit system? Another issue is that you may be running an ANSI build of wxWidgets. The released version of wxEuphoria expects a Unicode version. Building from source should make it all work. The configure script checks with your installed version of wxWidgets to make sure it gets all the compiler flags correct.
Actually I run a 64 bit and a 32 bit system on the same network, so I have access to both, but I've invariably found compiling leads to chasing dependencies, which to be quite honest, I don't really want to spend my time doing.
This is one of my bugbears with Linux - installing new programs (and printer support). I'm and 'end user' more than a pioneer, and in a perfect world I would like to download, install a new program, put a few required libraries in /usr/lib, and just go. If the program wants a library, the install script should know where to get it from. 64 bits shouldn't matter. I don't care about unicode.
[/quote]
Yes, I have played around with packaging it up to take care of that. Of course, different distros will have slightly different dependencies, etc. Yes, anything outside of your distro's package manager is hit or miss.
Matt
