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.

Sign up for GitHub

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

Jump to bottom

UberLogger does not show full callstack for unhandled exceptions #33

Open
Kalmalyzer opened this issue Aug 10, 2017 · 1 comment
Open

UberLogger does not show full callstack for unhandled exceptions #33

Kalmalyzer opened this issue Aug 10, 2017 · 1 comment

Comments

@Kalmalyzer
Copy link
Contributor

Kalmalyzer commented Aug 10, 2017 •
edited
Loading

With the current version of UberLogger, the callstack shown for unhandled exceptions is not very useful.

Example when I raise a NotImplementedException() deep within the codebase:

Unity callstack:
callstack-unity

UberLogger callstack:
callstack-uberlogger

The UberLogger callstack is not helpful for diagnosing where things went wrong.

I'll look into this myself in some days.
@Kalmalyzer
Copy link
Contributor Author

Testing again with Unity 2017.1.0f3, I am unable to reproduce it right now. It might be that this only happens under certain circumstances; will report back if/when I get a reliable repro case with the current codebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Kalmalyzer