Describe the project you are working on:
I am supporting Rider integration with Godot
Describe the problem or limitation you are having in your project:
When some managed exception in GodotTools happens, its call-stack is not printed to output.
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
When other users post their issues like
WARNING: EditorSettings::_get - Property not found: mono/editor/editor_path_optional
At: editor/editor_settings.cpp:151:_get() - EditorSettings::_get - Property not found: mono/editor/editor_path_optional
It is very hard to investigate without managed stack-trace.
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
Managed stack-trace should be printed to output.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
This is used very often in Godot Mono.
Is there a reason why this should be core and not an add-on in the asset library?:
It is core functionallity.
cc @neikeq
If you go to "Debugger > Errors" you should see the error there as well. If you unfold it, it should show the stack trace. Can you confirm if that works?
Nope, there is nothing there.


Hmm, looks like that only works for errors in the game not the editor itself.
Most helpful comment
Hmm, looks like that only works for errors in the game not the editor itself.