debug strategy

[Bang-Shiuh Chen]

All,

I have been working on the source code of cantera for a while, but it is difficult for me to debug. Do you have any suggestion or tool that I can use to improve the efficiency of debugging (both compilation and runtime) ?

Best,

Bang

[Ray Speth]

Bang,

What do you mean by efficiency of debugging? What is your current workflow for debugging? What kind of problems are you trying to debug? What operating system are you working on? Knowing this information would help in providing some relevant suggestions.

Regards,

Ray

[Ingmar Schoegl]

That's actually a fairly interesting question. I compile my own cantera fork within a docker container, and use the equivalent of this approach: https://rubberduckdebugging.com/, albeit without the duck. Jests aside, I mainly work through the python interface and tightly couple C++ code with corresponding cython wrappers, i.e. I can interactively probe behavior from ipython. I have used valgrind as a big gun if there's hard to track-down memory errors. Python code is easily developed within jupyter (inheritance!). I am aware that there are more sophisticated approaches, but rarely found a need for them. Nevertheless, it would be interesting to hear about other folks' approaches ...

-ingmar-