Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navigating to error line number in Rider from Godot editor debugger console is off-by-one. #61

Closed
knightofiam opened this issue Dec 20, 2020 · 4 comments · Fixed by godotengine/godot#45525

Comments

@knightofiam
Copy link

The error line number in the Godot editor debugger console that is referencing an attached script in Rider in the stack trace is correct, but double clicking the specific stack trace item containing a file name and line number (.i.e., ScriptName.cs:LineNumber @ method signature) navigates to the error line minus one in Rider.

@Flavelius
Copy link

It happens for me too, i hope it gets addressed.

@van800
Copy link
Collaborator

van800 commented Jan 28, 2021

Could you please add some step-by-step instruction on how I can show that debugger console with some stacktrace?

@Flavelius
Copy link

Flavelius commented Jan 28, 2021

Create a Simple script with more than one line that throws an exception, let it run in the scene, navigate to the Debugger -> Errors panel and click the respecting output.
grafik

@van800
Copy link
Collaborator

van800 commented Jan 28, 2021

Godot is starting Rider with the following commandline:
/bin/sh /home/ivan-shakhov/.local/share/JetBrains/Toolbox/apps/Rider/ch-0/203.6682.21/bin/rider.sh /home/ivan-shakhov/Work/godot-demo-projects/mono/dodge_the_creeps/Dodge the Creeps with C#.sln --line 20 /home/ivan-shakhov/Work/godot-demo-projects/mono/dodge_the_creeps/Main.cs
and so that line 20 is focused.

This issue can only be fixed on Godot side - I have created a PR godotengine/godot#45525

@van800 van800 closed this as completed Jan 28, 2021
akien-mga pushed a commit to akien-mga/godot that referenced this issue Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants