-
Notifications
You must be signed in to change notification settings - Fork 450
rust: report file and line number that caused a panic. #485
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
Conversation
Well, I guess a better approach is to move the panic handler to |
Using |
You're right, it doesn't have to have to be in the Updated the code. |
rusttest is failing. Pinging @ojeda -- is there a way to fix this?
|
|
I'm still getting the same error even with this. |
Maybe |
Doesn't work either. I'm reverting back to the previous implementation. I'll open a bug to move it to the |
|
At the moment we get a mangled call stack. This prints the panic message and source location. Moving the panic handler do the `kernel` crate allows us to use `pr_emerg` to print the panic info. Signed-off-by: Wedson Almeida Filho <wedsonaf@google.com>
Thanks, Gary! It looks like it's sufficient to exclude it on |
At the moment we get a mangled call stack. This prints a message that
allows us to pinpoint the source of the panic.
Signed-off-by: Wedson Almeida Filho wedsonaf@google.com