- Home /
Debugging logged errors with no stacktrace
Hi all
My project has started to spit out a lot of errors along the lines of:
Can't remove MeshFilter because SphereProportionActor (Script) depends on it
Unfortunately, this doesn't appear to be an Exception: it simply gives me the error message with no stack trace. Double clicking the error will not take me to the suspect line of code.
What is the best way to investigate these errors?
Thanks, Ves
By the way, I should clarify that I understand the error message. What I would like to investigate is the process that is attempting to remove the component.
Answer by slumtrimpet · Feb 05, 2015 at 08:37 PM
Answered here:
http://answers.unity3d.com/questions/396327/enable-stack-trace-in-non-development-builds.html
Your answer
Follow this Question
Related Questions
What are Asserts for? 1 Answer
Infinite terrain generation algorithm problems 1 Answer
3rd party bug reporting system similar to unity's "Report A bug" 3 Answers
Debugging with XInputDotNetPure 0 Answers
Debug Error,Debugging app 0 Answers