-
Notifications
You must be signed in to change notification settings - Fork 418
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
System.IndexOutOfRangeException
in OmniSharp.Utilities.PlatformHelper.GetMonoVersion
#2651
Comments
rene-descartes2021
changed the title
System.IndexOutOfRangeException in OmniSharp.Utilities.PlatformHelper.GetMonoVersion
Jan 28, 2025
System.IndexOutOfRangeException
in OmniSharp.Utilities.PlatformHelper.GetMonoVersion
Oh.. looking around in the issues I see that the net6 release should be used as I'd initially just looked at what I expect to see when something uses glibc:
However I get a different error now with
I guess I should just try building OmniSharp in this environment and see how that goes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error on download and run:
The
omnisharp-linux-arm64-net6.0
(non-portable build?) won't work for me as that is glibc. I am using bionic libc. So I tried what I expect to be the portable buildomnisharp-linux-arm64
.I believe I am using the "Linux Bionic Arm64 NativeAOT" vertical build of dotnet. I'm probably among the first to try using OmniSharp with this. It was compiled with
--use-mono-runtime
even though it targets linux-bionic, I'm really not sure how things work there with both Mono and CoreCLR.Oh, I just noticed
mono --version
doesn't print anything or error and it should?:Here is dotnet info:
Well any diagnostics I can try let me know. Might not be OmniSharp? Maybe dotnet was built with an unexpected problem by the Termux distro maintainer?
I plan to try to build a non-portable release of Omnisharp (for bionic libc) and see how that goes.
Thank you for looking and have a nice day.
The text was updated successfully, but these errors were encountered: