You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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?
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.
The text was updated successfully, but these errors were encountered: