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

Detect crashes from logs #83

Open
GeckoEidechse opened this issue Nov 15, 2024 · 0 comments
Open

Detect crashes from logs #83

GeckoEidechse opened this issue Nov 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@GeckoEidechse
Copy link
Member

Currently reaper is unable to detect a crash with a stack trace like e.g.

...
[2024-11-15] [23:29:25] [SCRIPT CL] [info] titan
[2024-11-15] [23:29:26] [SCRIPT CL] [info] 0.48 1
[2024-11-15] [23:29:26] [NORTHSTAR] [error] -------------------------------------------
[2024-11-15] [23:29:26] [NORTHSTAR] [error] Northstar has crashed!
[2024-11-15] [23:29:26] [NORTHSTAR] [error] 	Version: 1.28.4.0
[2024-11-15] [23:29:26] [NORTHSTAR] [error] 	EXCEPTION_ACCESS_VIOLATION
[2024-11-15] [23:29:26] [NORTHSTAR] [error] 	Attempted to write to: 0x9a83c70000
[2024-11-15] [23:29:26] [NORTHSTAR] [error] 	At: engine.dll + 0xfd391
...

instead it claims "No issues found"

It would be nice if it would detect the crash and maybe even print the most important bits of information, i.e. version number, first DLL and offset in the stacktrace, crash reason, etc.

@GeckoEidechse GeckoEidechse added the enhancement New feature or request label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant