-
Notifications
You must be signed in to change notification settings - Fork 1
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
Attempt to capture panics with GDB #690
Conversation
firmware-binaries/.cargo/config.toml
Outdated
"-C", "target-feature=+f", | ||
"-C", "force-frame-pointers=yes", | ||
"-C", "force-unwind-tables=yes" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add an XXX: Seem to be ignored
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, can do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait the other flags also seem to be ignored right? When we add gooblygook there, we don't get any warnings or errors.
We think #690 fixed our nightly issues. At the very least, we cannot reproduce it locally anymore. However, we've also seen that nightly fails more often than local runs, so we'll run nightly a bunch of times in the coming days to see if we've actually fixed things.
We think #690 fixed our nightly issues. At the very least, we cannot reproduce it locally anymore. However, we've also seen that nightly fails more often than local runs, so we'll run nightly a bunch of times in the coming days to see if we've actually fixed things.
There's still some issues here, e.g. it seems like the maximum stack trace depth on a panic is 2 no matter what I try, but otherwise it seems to have reduced the number of times the TCP test fails (likely by replacing
start
withcontinue
in the GDB script). Otherwise, this PR:firmware-support
that provides a method that GDB canbreak
on (though it should preferentially break oncore::panicking::panic
orrust_begin_unwind
for the time being) in order to grab a backtrace of the program and exit.