Topic: Truncated ERROR - FATAL EXCEPTION output makes debugging harder

Hello, I'm having troubles debugging my modifications to a tribe LUA, because the output error has the stack trace truncated. As you see below, just when the error is displayed the output is cut.

I'm pretty sure this is some limit in the error output length, can it be fixed? This happens in the Widelands version 1.2~rc1 Release but I had this problem since previous versions. The fix should be pretty easy as it only needs needs to increase the output length.

Here is an example of what I get:

[00:08:22.384 real] ERROR: ############################## [00:08:22.384 real] ERROR: FATAL EXCEPTION: Error while loading tribe 'europeans': [/run/build/Widelands/src/scripting/lua_errors.cc:21] tribe europeans: Failed adding building 'europeans_stonemine_basic': [/run/build/Widelands/src/scripting/lua_errors.cc:21] [/run/build/Widelands/src/scripting/lua_errors.cc:21] [/run/build/Widelands/src/scripting/lua_errors.cc:21] [/run/build/Widelands/src/scripting/lua_errors.cc:21] [/run/build/Widelands/src/scripting/lua_errors.cc:21] europeans_stonemine_level_4: Error in productionsite program mine_granite: Erro [00:08:22.384 real] ERROR: ##############################

Thanks.

Top

Quote

If there is a limit set on the length of the output or the size of the buffer for error messages, it might be possible to increase it by modifying the source code of Widelands. This would involve changing the buffer size where the errors are handled and displayed.
You would need to locate where the errors are printed in the code, likely in geometry dash breeze the lua_errors.cc file or similar, and look for any fixed-size buffers or string truncation logic. Adjusting this value and recompiling the game might solve your problem.

Top

Quote