Some errors will allow you to compile, but the routine won’t work once the code is hooked and running because there is some violation of the array and pointer conventions.
In the DEFINE_HET_RXN_RATE example from the Fluent customization manual, I see the thread declarations as follows:
Below are yours:
The space between ‘Thread’ and ‘*’ may be changing the meaning of these lines at runtime, where the compiler just parses these and thinks everything is just fine.
The code will usually proceed until the fatal error, so you could also try a few debugging write statements sprinked throughout the UDF to let you know what the last lines before the crash are.
I hope this helps.
Please Login to Report Topic
Please Login to Share Feed