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

Non-fatal signals treated as fatal #1390

Open
dfoxfranke opened this issue Sep 21, 2023 · 3 comments
Open

Non-fatal signals treated as fatal #1390

dfoxfranke opened this issue Sep 21, 2023 · 3 comments
Assignees

Comments

@dfoxfranke
Copy link

I'm trying to use tarpaulin to get a coverage report for my crate hw-exception. This crate is designed for, among other things, handling and recovering from segfaults. Unsurprisingly, it has tests which segfault, and then recover. Tarpaulin, however, panics as soon as ptrace notifies it of the segfault, without seeing whether the program being traced is going to handle the signal. It is therefore unable to give me a useful coverage report.

@xd009642
Copy link
Owner

If you run with --engine=llvm you may circumvent a lot of complexity with handling signals. Provided this isn't another edge case llvm coverage fails to handle.

@dfoxfranke
Copy link
Author

Thanks, that did the job. Feel free to close this issue or to leave it open if you care to address the ptrace engine.

@xd009642
Copy link
Owner

Good to hear 👍

I'll keep it open for now to remind me to investigate, if it proves too tricky to do with ptrace I'll close it later on as a won't fix and just recommend people use --engine llvm

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

2 participants