Skip to content

Ability to choose log detailed crash reason #90

Closed
@easylogging

Description

@easylogging

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.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions