-
2026 staff recruitment is open! Check it out and consider applying!
Linux item const error
- Thread starter vingo
- Start date
The SIGSEGV message is the operating system complaining about a memory reference error in an executable.
It probably occurred in the C++ code that implements object Item , method getTile().
If you don't know what that means you can't debug it.
It could be a bug in OT's code. if so the OT C++ coders know how to find/fix such things.
It could be caused by using mixed versions of OT, in which case recompiling with consistent source will fix it.
Or it might be "nine of the above" - there are a lot of ways to get a sigsegv
It probably occurred in the C++ code that implements object Item , method getTile().
If you don't know what that means you can't debug it.
It could be a bug in OT's code. if so the OT C++ coders know how to find/fix such things.
It could be caused by using mixed versions of OT, in which case recompiling with consistent source will fix it.
Or it might be "nine of the above" - there are a lot of ways to get a sigsegv
It might be initiated by something in an xml or a script, but that would still be a bug in the C++ code, which should be protected from that kind of thing. At least when the OT code is "production ready" 
If you're using pre-production code all bets are off.
If you know how to write LUA code, write a script that calls that function in different ways (including passing nil parameters, messed up XMLs etc, to test the error protection). If you find a pattern you on your way to understanding the problem.
If you're using pre-production code all bets are off.If you know how to write LUA code, write a script that calls that function in different ways (including passing nil parameters, messed up XMLs etc, to test the error protection). If you find a pattern you on your way to understanding the problem.