[Astrodan]

Hello there,

I just tried to use the expressionToFace function of the swakTopoSources Library. Since I made (several) mistakes it didn't work, so I checked for DebugFlags and found ExpressionResult.

However, everytime I combine this debug flag and (at least) libgroovyBC.so in my controlDict, every single OpenFOAM tool ends with a segmentation fault, although most of them perform their job normally.

I by now figured I can solve the problem by using the debug flag to correct my expression, and then running the simulation without the flag, but this would not be possible when the expression is actively used in the simulation, since the simulation itself does not abort when the debug flag is active.

The segmentation fault can easily be reproduced when adding the lines

DebugSwitches
{
     ExpressionResult    1;  
}

libs
(
     "libgroovyBC.so"
);

to the controlDict of e.g. the cavity case (no further changes necessary, just add and run blockMesh). Although here apparently the solver works.. maybe it's a problem in my case, I attached my solver log.

Has anyone else come over this problem?
And yes, I'm aware that this is kind of a bug report, but the swak4Foam report site demands a registration, and I'm kind of annoyed of having to register at every bloody side.

[wyldckat]

Quick answer: If I remember correctly, debug switches in swak4Foam are a bit different.
Go into the folder "swak4Foam/Examples" and run the following command:

grep -ir "debug" *

this will give several examples on how to use the debug system that swak4Foam uses.

In the folder "swak4Foam/Documentation" you will also find more details about the debug switches available in swak4Foam.