Add logs for Unigine Script in the case of Editor/Game crash

[Klimczak.Jan]

Hi,

At the moment it is very difficult to detect a problem with Unigine Script in the case of Editor/Game crash because it's not log the place of problem. It should be somewhere possibility to enable/disable logging the last execution point of Unigine Script in the case of crash. It could be enough even to have the line number and file name of Unigine Script execution (the full Stack trace would be perfect).

At the moment the only way is to try to detach all Unigine Script, and execute some part of the script, run it, and in the case of crash, repeat it (also reload world, etc.). It is very time consuming ... And in the case of SDK update it is necessary to quick update US to work with it. Without logging the file and line number of problem it is almost impossible.

Cheers 

[silent]

Hi Jan,

Are you using release builds? Debug binaries should log the file and line number in case of script crash.

[Klimczak.Jan]

Hi Silent,

I am using debug version:

and the only log about crash which I see is:

so I really don't know which my Unigine Script fail and where it fail 

Such logs are printed when this crash Editor but the only way I see the file name and line number of error for Unigine Script is the case when such error not crash Editor/App.

[silent]

Hi Jan,

Thanks for the clarification. That's indeed should be achievable. I will create a feature request in our internal bug tracker regarding this.

[Klimczak.Jan]

Thank you @silent :)

ps.

for test cases you can use this issue: https://developer.unigine.com/forum/topic/4955-animations-crashes-editorapp/ :)

Edited July 23, 2018 by Klimczak.Jan