lix-project/lix

Print bug report instructions and stack trace on SIGABRT/SIGSEGV #229

New issue

Open

opened 2024-04-08 01:37:49 +00:00 by jade · 1 comment

jade commented

2024-04-08 01:37:49 +00:00

Owner

Programs like Clang and others print bug report instructions when they crash, along with stack traces. Lix could do this too, and it would probably generate more useful reporting instructions.

I think there has been another filing or at least discussion of using a stack tracing library to implement this.

Programs like Clang and others print bug report instructions when they crash, along with stack traces. Lix could do this too, and it would probably generate more useful reporting instructions. I think there has been another filing or at least discussion of using a stack tracing library to implement this.

jade added the

labels 2024-04-08 01:37:49 +00:00

qyriad added this to the v2.91 milestone 2024-05-13 03:06:34 +00:00

jade modified the milestone from v2.91 to post-release

2024-08-13 01:19:36 +00:00

cobaltcause referenced this issue

2024-10-08 16:01:39 +00:00

Crash during nixos-rebuild #542

jade commented

2024-10-08 18:47:36 +00:00

Author

Owner

fixed by https://gerrit.lix.systems/c/lix/+/1854 for std::terminate; segv and abrt are pending making a separate error reporting process

fixed by https://gerrit.lix.systems/c/lix/+/1854 for std::terminate; segv and abrt are pending making a separate error reporting process

Sign in to join this conversation.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#229

No description provided.