LeCom wrote:So, 64 bit means 64 bit address bus and 64 bit register size. So this means that int is still 32 bit on 64 bit systems? Sheet, now how fucking gay is that.
Well, I would fix it if I still had the motivation to work on it, but well I probably should advertise it somewhere where it will actually be seen or something. Btw how come it crashes being a 32 bit application? Don't 64 bit CPUs have a 32 bit emulation mode?
The server crashes when run with a 64-bit Python loading a 64-bit libenet.so. It works fine in 32 bits.
Seriously, set up a 64-bit VM in Qemu or something and pick a fairly lightweight distro.
longbyte1 wrote:Do you happen to be cutting corners in your test environment?
No. The code is not 64-bit clean, so when I try to run the server natively it crashes, but when I run the plebserver in Wine it works... and the last time I tried compiling the code there were a LOT of errors pertaining to mismatched type sizes, mostly surrounding size_t.
longbyte1 wrote:We should move on to create our own replicas of AoS instead (call them "tributes" if you'd like): we learn far more and take far less time making it ourselves than trying to reverse engineer a heavily obfuscated, hand-optimized work of art.
Sure you're using a 64 bit cvxl.so?
Aside from me having absolutely no experience with these VMs, I'd also have to free some space on my disk and set one up and it's not worth the result right now. In the long run, I have access to a 64 bit machine once a week which I can use to change my code. Can't you simply use 32 bit emulation until then? It's not like my stuff is the only software that isn't 64-bit-ready.
But I'd rather fix the issue so I don't have to use it.
longbyte1 wrote:We should move on to create our own replicas of AoS instead (call them "tributes" if you'd like): we learn far more and take far less time making it ourselves than trying to reverse engineer a heavily obfuscated, hand-optimized work of art.