elwardi
04/02/2025, 12:04 PM-ggdb -O0) then gdb can:
- set breakpoints by line numbers and function names (br file.C:<line>, br main ... etc)
- explore objects as they are in memory once a breakpoint is hit
you should be able to do this with the VSCode debugger too, but compiling with debug flags is important
- for this use case, you probably need to compile the finiteVolume lib in debug mode, so you can inspect fields
instead of listing hundreds of values, i usuallly
- create debug fields as NO_READ NO_WRITE ones
- use if (debug) { field.write(); } so i get it into paraview
- from there either visualize or run some stastics analysis