Closed samseaver closed 12 years ago
OK, I'm closing this issue, I just realized that the script created to run the toolkit, runMFAToolkit.sh, actually sources bin/source-me.sh, and thus the environment variables are there when run. I've just not run
source bin/source-me.sh
before starting up GDB
Environment variables, such as ARGONNEDB, which are used by the MFAToolkit, but are set in ModelSEEDbootstrap.pm, are only set for the lifetime of the PERL job, and thus, when trying to debug/run MFAToolkit separately, one must explicitly set these environment variables.
Unfortunately for the user, if these aren't set, one only receives a seg fault for their trouble, so either the run_MFAToolkit.sh command does this, or its encoded, in turn, in the C++ code.
Or it can be added to bin/source-me.sh as an alternative.