• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!
  • 2026 staff recruitment is open! Check it out and consider applying!

Linux Debian how to generate better crash dump file?

Tbol

Well-Known Member
Joined
Apr 7, 2019
Messages
625
Reaction score
71
Hello! Right now, I’m compiling my source without any debug flags, just using commands like make clean and make -j4. As a result, when my server crashes, it generates a rather useless crash dump file that doesn’t provide much useful information. Is there a way to compile the source with some kind of debug flags that would produce more detailed crash dump logs? Logs that would help me pinpoint exactly—or at least more accurately—which part of the code is causing the crash?

Currently, when I get a crash log, I only know which function caused it. But since there are 100+ Lua files using that function, it’s very difficult to find the exact problematic code, especially if I overlook something. So, I’m looking for a better solution, that would make my life easier
 
I’m compiling my source without any debug flags
What engine do you use? Can you link github of clean version of that engine, so we can check what kind of build process it uses (cmake, ./configure etc.)?
it generates a rather useless crash dump file that doesn’t provide much useful information
Can you post example crash report? So we could know, which kind of build you are using now.
 
Back
Top