-
Notifications
You must be signed in to change notification settings - Fork 558
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
"Exception: System.Exception: Native code encountered, plug required. Check build output for more information." when trying to use Exception.StackTrace or Exception.Source #3145
Comments
Have you checked that Cosmos.Plugs is present in the csproj? |
And for normal debugging i would just use 'try catch' statements |
Those may not be plugged as far as i know |
I can use try-catch, but it won't give me a source or a stack trace, just the error |
do you have the devkit? you could search for the exception class plugs to see what actually work on that class |
That looks like it just means that you can't use those methods. Also, I just discovered this post which seems to be talking about the same thing: #1851 |
So right now it is not plugged |
I am just guessing, but for that property to work you would first need an implementation for the methods of the image |
Which is why I posted this, because I don't really understand how plugs work, other than that they are placeholders for features that haven't been implemented yet. So I probably can't implement them myself. |
You basicly could, but it would take some time and effort. Or just ouy also could Make plugs For it |
It's never been plugged. |
What is the usecase for this plug
Debugging errors. Stack traces and sources are very important when it comes to debugging, as they indicate where an error is coming from.
Complexity of plug
I don't know, I'm not very familiar with machine code and binaries and things like that.
Describe alternatives you've considered
I don't know of any alternatives I can use, since the normal debugger just gives me memory addresses, which aren't very useful.
Additional context
I just want to be able to use Exception.StackTrace and Exception.Source, and any other methods and properties that are affected.
The text was updated successfully, but these errors were encountered: