Error initializing after compile ubuntu 22

[leo36dff]

After following the entire tutorial i tried to compile on ubuntu 22

it compiles with no error, but when i try to give ./ot(whatever) it shows core dumped...

[Codinablack]

Which tutorial, the one on the wiki?

That thing was just a copy and paste job of gesior's instructions on how to compile it. It was put there as a temporary guide.

I don't know why it would immediately core dump unless you ended up grabbing mismatched libs (for a different architecture or platform).

There is also no instructions anywhere that says to run it you type

./ot

not sure where you got that from... if you simply renamed the outputted executable, then yeah that would make sense, but the screenshot you show, it doesn't not show anything like that, looks like you just compiled and immediately typed in some unknown command.

My suggestion, if it's not a simple mismatched lib or name, then I would try to revert everything and go back to a clean state that you were in before doing anything, and use the bootstrap.sh to install and setup the server. It's what it was made for!

I guess many don't know about it yet, but the bootstrap.sh is the way to go, it was created with the intention of simplifying the process to getting started on ANY linux machine out there, and has been tested across MANY different OS's and on both x64 and ARM64 architectures...

The above reminded me... we don't support 32 bit builds, so if you tried to do the entire process using 32 bit libs and stuff instead, then that could also be a reason you are running into this problem

[leo36dff]

Thx for reply Cod, yea, i renames it to ot lol. I use this github Wiki page using vcpkg and premake, didnt know it wereca copypaste of tfs or whatever, i will try again and post the news. Ty. Using ubuntu 22 x64

[leo36dff]

Fresh start, updated ubuntu 22, everything installed like vcpkg, bootstrap etc. Using now bootstrap.sh It says everything ok but after... core dumped... You want any any specific information or print? All far as i know what i did ive already described it here.

[leo36dff]

BTw my vps config. ubuntu 22 fully upgraded

[Codinablack]

If you could share the core dump that would be helpful in determining the problem.

What architecture is your OS running on?

[Codinablack]

Yes I just did a quick search and that seems to be the common reason this happens:

Seems to me you chose x64, and are running on ARM64 VPS most likely

[leo36dff]

Im running a x64 xeon processor. Share my core dump? Idn what it means. No log created/found, im compiling right now on debug mode, i will post here soon.

[leo36dff]

Updating:

1: step

2: step

3: step

All files generated sucessfuly on debug mode.

[Codinablack]

The generation of the files is not a problem. The compiling is not a problem.

The problem is most certainly a mismatch on architecture somewhere, or lack of support for the AVX specified.

The core being dumped is supposed to be in the location /var/lib/apport/coredump or /var/crash I'm not sure which is the correct location, it may be that your machine has a different location configured. You need to find that, and you also need to use GDB to analyze it to provide some valuable information about what led to the crash.

I am not a linux super user. Just searching that error results in all replies saying its a cpu architecture mismatch or a problem with the cpu not supporting the specified AVX. That's it. Nothing to do with this project in of itself, but rather with the configuration on your side. You could try adjusting or removing the specifications for AVX in premake5.lua, but I am doubtful that is the problem. Even though your terminal is showing you running a x86_64 type CPU, I still believe it's going to come down to an issue with the wrong architecture selected somewhere along the way. Either a lib, or all the libs, or entire project (most likely).

Changing between debug and release shouldn't matter at all, and if it does, then that is a for sure sign that there is a problem with the dependencies.

Anyway it goes, I can't really resolve that problem for you; at best I can try to identify the problem with you if you provide more information, but ultimately I have already told you the possible issues, its going to be up to you to figure out where something went wrong.

I have had many users use that script without any problems getting set up. There is even a guy who has an entire kubernates cluster running on ARM64 based, free servers. The person who wrote the script actually tested out nearly 20 versions of linux, and on mulitple machines, even used the script to install black tek server on his phone... he is a linux super user for sure, but sadly I am not.

[Codinablack]

The workflow I have produces a binary for ubuntu 22. If all else fails, you can just fork this repo on your github, edit the workflow to save the binary somewhere and run it, because its producing binaries without failure. I plan to eventually add to the workflow to store the produced binaries but right now I have a lot of other things that are calling priority, like the finishing of this system I have been building for months, and fixing all the bugs on this repo.

It should be pretty straight forward, to push the binary somewhere, just lookup a tutorial or some example code on how to upload a binary or "nightly" sometimes they are referred to as... and then you can just download the binary.

[Codinablack]

I asked chatGPT if there were any other possibilities for this to be happening, and although he mentions a couple, they are quite unlikely, and the others are the same as what I was saying anyways, but he offers some advice on how to debug further, perhaps you can find him useful for helping with this problem, here is that specific chat.

https://chatgpt.com/share/673ff347-4358-8000-8614-fb6cf0ddac98