-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stack smashing detected; terminated #5
Comments
Github has the latest code. Did you use any configure options? What compiler
is being used?
See if "./src/xu4 -h" runs without crashing. Does the Boron interpreter you
built run? Does the Linux snapshot from http://xu4.sourceforge.net/
download.php run on your system?
|
The compiler is No configure options. The binary from .net does not crash with the same error, but complains: |
Please let me know what happens when "./src/xu4 -h" is run.
What version of Allegro are you using? On Ubuntu the liballegro-acodec5.2
package is also needed. The README in the snapshot archive has instructions
for installing Allegro on Ubuntu.
|
These are the liballegro packages installed:
$xu4 -h provides normal output (from both my repo build and the downloaded version), but the other options still core:
xu4 -v finds/opens it's dependencies before crashing, fwiw. Thanks for walking me through this. |
What is the -v output? The latest Allegro is version 5.2.7.
|
I'll try building Allegro 5.2.7 from source, the base repo doesn't have that build yet, and the PPA from Allegro doesn't have impish builds. The -v output is:
|
Are you able to run gdb? I'd try that before building Allegro.
|
If you can't debug the program here's a patch to narrow down the point of failure. Based upon the verbose log, configInit() is probably failing.
|
Confirmed your suspicion about configInit():
I have made some progress (of a sort). Muddling my way around gdb (in over my head, in case it wasn't obvious) it looked like init was stepping through some libboron "stuff". I had also seen in the makefiles that some of that was avoided if I used the
That seems to be a detour from the original issue, but thought it might help narrow things down at least to know that cutting out boron changes things significantly. Happy to provide more specific |
I installed a Pop!_OS VM and tracked down the issue. This is a Boron bug which I have just pushed a fix for. The Makefile was also broken on Pop! and a shared library (the default) got installed into the wrong directory. Thanks for your report. I have also asked @SiegeLord to update the PPA for Ubuntu 21.10. |
Thanks for your guidance and for tracking the bug down. I look forward to some classic Ultima nostalgia! |
After some challenges building from the github repo (which may admittedly be the source of my problem here) on pop_os 21.10 I've managed to get to a complete build, but now the xu4 binary aborts with
The build is mostly clean with a few warnings of the type:
warning: format not a string literal and no format arguments
but no other errors.
Dependencies were satisfied as follows:
From system packages:
libsdl2-2.0-0
libsdl2-dev
libxml2
libxml2-dev
liballegro5.2
liballegro5-dev
From sourceforge:
libboron https://sourceforge.net/p/urlan/boron/code/ci/master/tree/
any suggestions would be much appreciated
The text was updated successfully, but these errors were encountered: