ID:2249117
 
BYOND Version:511
Operating System:Linux
Web Browser:Chrome 58.0.3029.110
Applies to:Dream Daemon
Status: Open

Issue hasn't been assigned a status value.
Problem Summary:
When attempting to run a Space Station 13 dmb with DreamDaemon on an Ubuntu 16.04.2 Server I get a "Crashing due to an illegal operation!" on a New() call.

Here is the complete trace:
https://gist.github.com/anonymous/ 662fb1ba91d2d3d44ebb115cc88db41c

The devs of this Space Station 13 fork were of the opinion this is a bug with BYOND on Linux, and to post it here.


Steps to Reproduce Problem:
On a clean Ubuntu 16.04.2 Server Virtual Machine running in VirtualBox on Windows 10, Following this guide: https://www.reddit.com/r/SS13/comments/5xk7xv/ making_a_ss13_linux_server_in_aws/ I'm trying to set up a Space Station 13 server on a local Ubuntu 16.04.2 Headless Server Virtual Machine.

After successfully installing BYOND 511.1370, pulling the repo, copying the contents of config/example/ to config/ and compiling the dmb, I run `sudo DreamDaemon /Path/To/paradise.dmb 3333 -trusted` and get the trace above.

I have tried a clean Ubuntu 64 bit 16.04.2 server VM with the following dependencies:
sudo apt-get -y install make htop  git unzip build-essential
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get -y install lib32z1 lib32ncurses5 libmysqlclient-dev:i386

As well as a clean Ubuntu 32 bit 16.04.2 server VM with only the first line of dependencies (since it already is i386).


BYOND Versions Tested:


REALLY important ya probably should've linked this: https://github.com/ParadiseSS13/Paradise
In response to PJB3005
PJB3005 wrote:
REALLY important ya probably should've linked this: https://github.com/ParadiseSS13/Paradise

My bad. It was linked in the reddit thread whose steps I said I was following.

After some retesting here is the current list of errors:

Paradisess13 (ERROR)


I also tested tgstation ( https://github.com/tgstation/tgstation ) and Baystation12 ( https://github.com/Baystation12/Baystation12/ ), both of which seem to at least start up correctly on my current setup.
I'll look in on that trace tomorrow, but I'd be surprised if it's not the same issue as id:2245438. The fix I have for that currently in 1384 is incomplete, so 1385 should fix it. But I'll take a look at this just in case it's a separate issue.