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
Indeed it would, but Clar is meant to run in both Linux (GCC, Clang) and Windows (MSVC), and as far as I know there's no straightforward or crossplatform way to print this kind of traces in both platforms. :(
Indeed, this would be useful, but it's really the thing that you're testing that needs to produce the stack trace. I'd be happy to support simplifying this as much as possible, but fundamentally cl_assert(...) just calls a function. If that function fails 15 calls deep, you need a way to report that up. This means either your app knowing how to report it to clar, or clar knowing how to get that information from your app. Simply calling backtrace() won't help once the call has exited and we know that we've failed.
I'm closing this but if you have a concrete plan for more general support that would be 👍
It'd be useful when clar would print out a stack trace that lead up to the failed test.
The text was updated successfully, but these errors were encountered: