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

Rust Backtraces? #691

Open
rslawson opened this issue Dec 4, 2024 · 0 comments
Open

Rust Backtraces? #691

rslawson opened this issue Dec 4, 2024 · 0 comments

Comments

@rslawson
Copy link
Collaborator

rslawson commented Dec 4, 2024

In PR #690 I introduced a GDB script that should be able to grab backtraces when Rust code panics in the TCP test. However, despite my best efforts, those backtraces are limited to a depth of 2, and one of the displayed functions is invariably core::panicking::panic (or related). I'm not sure if this is because something is ignoring panic = "abort", or if the -C force-unwind-tables=yes -C force-frame-pointer=yes options are being ignored somehow, but this is definitely worth investigating.

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

No branches or pull requests

1 participant