[hansel]

I'm having a problem with at segmentation fault in turbDyMFoam. I'm attempting a rotating mesh and something about moving that mesh is causing the fault, with no error or warning message. I would like to gather more information on the cause of the fault.

I can fire up GDB and get the name of the routines it was in, but that's not very useful. I have 2 questions:

1) Is there an option to turbDyMFoam to give more debugging information?

2) Is there an easy way to compile in debug mode. I have developed unix (solaris) code, but I only used makefiles. These huge trees with wmakes and cmakes are strange to me. Is there a master options list somewhere?

Thanks
Steve

[henrik]

Dear Steve,

in $FOAM_SRC/../etc/cshrc you find

# WM_COMPILE_OPTION = Opt | Debug | Prof
if ( ! $?WM_COMPILE_OPTION ) setenv WM_COMPILE_OPTION Opt
#if ( ! $?WM_COMPILE_OPTION ) setenv WM_COMPILE_OPTION Debug
#setenv WM_COMPILE_OPTION Opt
setenv WM_COMPILE_OPTION Debug

Uncomment the last line. Resource. Make sure WM_COMPILE_OPTION is set correctly. Compile Everything. Compile your code.

This adds full debug information to your library and executables which you can use "gdb" OR "valgrind --tool=memcheck" on. I find the latter very useful for finding memory violations.

Here are also a few links that I found quickly after googling "openfoam debugging".

http://www.tfd.chalmers.se/~hani/kurser/OS_CFD_2008/debugging.pdf
http://openfoamwiki.net/index.php/HowTo_debugging
http://powerlab.fsb.hr/ped/kturbo/Op...ngTraining.pdf

Good luck hunting

Henrik

[hansel]

Thanks for the reply. I actually found my problem, but I will keep this information for the next one that comes up.

Steve