Hi, question about jassert - normally it stops program execution when the assertion fails and prints out a message.
For some reason, sometimes it only prints out the message and doesn’t stop execution - anyone any ideas why this would be?
Thx
It should only stop execution if a debugger is attached. In your case is a debugger attached? if so could you give more details about your setup? OS, IDE, versions you’re using, are you attached to a host, etc?
Hi, yes, debugger is attached.
Mac/OS 14.4, Xcode 15.4
It’s strange in the fact that some jasserts to stop, some don’t. i don’t really understand the mechanism of how jassert causes the degugger to stop so can’t really investigate myself.
Are you perhaps running some of your code in a different process than the one where you have attached the debugger? For example, are you hosting a plug-in in a separate process than the DAW?
hi, no it’s a single threaded standalone app
I’m unsure if this is related, but I have had times when breakpoints and jassert(false) have not been triggered in debug builds in CMake projects when launched from Clion. Deleting all the build folders has fixed this. You have probably already done this.