This is saying that the exception handler that is used for Cilk functions is seeing an exception other than a C++ exception, which is illegal since we have no idea how to handle it.

If you can reproduce the problem, you can set the Visual Studio debugger to break when an exception is thrown which will allow you to determine what's happening. If I had to guess, I'd say that there's an access violation occurring that's propagating up.

What you might try is adding a catchall handler to your spawned function to at least report on any non-C++ exceptions.

I'll look at modifying the code to at least tell you what the exception ins.

- Barry

Hi Daniel,

I've seen this come up a couple times due to issues with the optimizer. Has your coworker ever seen it with a /Od or -O0 build?