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

Feature request: break on fail. #14

Open
jamiebullock opened this issue Mar 19, 2019 · 2 comments
Open

Feature request: break on fail. #14

jamiebullock opened this issue Mar 19, 2019 · 2 comments

Comments

@jamiebullock
Copy link

It would be super-helpful if pluginval had the option to break inline when tests fail so that the source of the failure can be traced. Something like equivalent of the "-Wfatal-errors" compiler flag. I know this can be achieved currently by placing assertions in the relevant places, but this is a bit of an awkward workflow.

@drowaudio
Copy link
Contributor

I think you can achieve this by compiling from source and enabling the UnitTestRunner::setAssertOnFailure option.

If you want the assertions to kill the app you can do this by defining JUCE_LOG_CURRENT_ASSERTION to terminate?

@jamiebullock
Copy link
Author

@drowaudio Thanks. I was aware I could edit the source as described. My suggestion was to include this as an option in the pluginval UI to avoid the need for recompiles etc.

But... setAssertOnFailure isn't actually helping in my case. I'm trying to track down the source of of Illegal allocations / deletions but when at the point where the assertion terminates the call stack doesn't go through my code. I'm guessing tracing the source of illegal allocations in this way isn't possible?

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