-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Allow for running non-test binaries #507
Comments
@DenialAdams, in develop I've added a I'd have liked to get the --print-rust-flags command to just print a single line however different configs can result in different rust flags so tail is just there to print out the last one printed. Once it works like that I'll then look at refining the usage but it should be workable via a potentially ugly config file listing a call to your binary as a config. |
Created a draft PR with my first work on this. #604 It should work fine for basic usage |
Ah no that's covered by #107 an older issue. Though it is something I will start working on this month it's just moderately fiddly (need to capture the process spawn, read /proc/pid, add some extra tracing logic) |
Also, I aim to do #612 next as the relocation mode could complicate those test setups anyway and lead to failures to get any coverage data and spurious failures even if I did get it working |
pretty sure this is now solved so just going to close it |
If a user is using a non-cargo build system for rust but has a built and instrumented binary they should be able to collect coverage for it. This issue is for tracking that feature. I've identified two approaches that could work:
Edit: removed some unnecessary noise
The text was updated successfully, but these errors were encountered: