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

Ability to choose log detailed crash reason #90

Closed
easylogging opened this issue Aug 18, 2013 · 1 comment
Closed

Ability to choose log detailed crash reason #90

easylogging opened this issue Aug 18, 2013 · 1 comment
Milestone

Comments

@easylogging
Copy link
Contributor

When crash is handled, we need to give user ability to log detailed reason or not.

Reason like in following last two lines

18/07/2013 12:56:03,756 FATAL [default] CRASH HANDLED; Application has crashed due to [SIGSEGV] signal
    Invalid access to memory
    Program is trying to read an invalid (unallocated, deleted or corrupted) or inaccessible memory.

means

    Invalid access to memory
    Program is trying to read an invalid (unallocated, deleted or corrupted) or inaccessible memory.
@easylogging
Copy link
Contributor Author

This will be disabled by default (6a99807)

@abumq abumq closed this as completed in f13b042 Aug 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant