Skip to content

Conversation

@a-nogikh
Copy link
Collaborator

We need to look for the error type after the "rust_kernel: panicked" line.
Ignore some common irrelevant frames.

We need to look for the error type after the "rust_kernel: panicked"
line.

Ignore some common irrelevant frames.
@a-nogikh a-nogikh requested a review from tarasmadan June 20, 2025 10:39
@a-nogikh a-nogikh added this pull request to the merge queue Jun 20, 2025
Merged via the queue into google:master with commit 9bb62db Jun 20, 2025
17 checks passed
{
title: compile("rust_kernel: panicked"),
report: compile("rust_kernel: panicked at [^\n]*?\n(.+?)\n"),
fmt: "%[1]v in %[2]v",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is hard to distinguish. All other titles have unique prefixes.
"rust_kernel panicked: %[1]v in %[2]v" for example.

I'll include this change in my PR to not forget.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if the unique rust_kernel panicked prefix will help a lot with setting the type - it's not a single "rust crash" type, there are many options, which are totally different:

  • null pointer dereference occurred
  • attempt to subtract with overflow

It's not useful to combine these all into one category either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants