Uh oh!
There was an error while loading. Please reload this page.
rust: report file and line number that caused a panic. - #485
Conversation
nbdd0121
commented
Aug 19, 2021
Well, I guess a better approach is to move the panic handler to |
nbdd0121
commented
Aug 19, 2021
Using |
wedsonaf
commented
Aug 19, 2021
You're right, it doesn't have to have to be in the Updated the code. |
Uh oh!
There was an error while loading. Please reload this page.
wedsonaf
commented
Aug 19, 2021
rusttest is failing. Pinging @ojeda -- is there a way to fix this? |
nbdd0121
commented
Aug 19, 2021
|
wedsonaf
commented
Aug 19, 2021
I'm still getting the same error even with this. |
nbdd0121
commented
Aug 19, 2021
Maybe |
wedsonaf
commented
Aug 20, 2021
Doesn't work either. I'm reverting back to the previous implementation. I'll open a bug to move it to the |
nbdd0121
commented
Aug 20, 2021
|
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>
wedsonaf
commented
Aug 20, 2021
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