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

MONO_ENV_OPTIONS needs better documentation #585

Open
mattjohnsonpint opened this issue Jul 13, 2022 · 3 comments
Open

MONO_ENV_OPTIONS needs better documentation #585

mattjohnsonpint opened this issue Jul 13, 2022 · 3 comments

Comments

@mattjohnsonpint
Copy link

mattjohnsonpint commented Jul 13, 2022

I stumbled across MONO_ENV_OPTIONS in the 2.8 release notes. I also see it mentioned once in the LLVM docs page, but nowhere else.

This seems like a pretty fundamental feature. Shouldn't it be highlighted somewhere more prominent?

In my case, I was able to set MONO_ENV_OPTIONS="--debug" so I can get filenames and line numbers when running tests under mono using dotnet test (when the test project targets .NET Framework and runs on Linux/macOS).

I found mono --debug in the debugging docs, but couldn't figure out how to get it passed through with dotnet test until I found MONO_ENV_OPTIONS.

@lambdageek
Copy link
Member

@akoeplinger I wonder if we can format the mono manpage and put it somewhere useful either on the mono website, or in the .NET docs.

Googling around, the online copies of the manpage are usually pretty out of date, and folks using modern .NET 6+ Mono don't install the MDK, so the manpage isn't available locally.

@mattjohnsonpint
Copy link
Author

I didn't think to check the man page. lol.

@akoeplinger
Copy link
Member

Yeah I've been thinking about this as well, either the mono website or the .NET docs is fine with me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants