enabling debug logging revealed that some debug logs hadn't been updated in a while.
also had to re-learn a_sprintf class.
new overload report has some new classes or categories and changes approach on a couple things. it may change a bit more soon as we rotate some names around in the cloud (nuage)
blowfish_crypto::~blowfish_crypto()
{
- FUNCDEF("dtor");
+ FUNCDEF("destructor");
LOG("prior to key whack");
WHACK(_key);
LOG("after key whack");
rsa_crypto::~rsa_crypto()
{
- FUNCDEF("dtor");
+ FUNCDEF("destructor");
LOG("prior to rsa free");
auto_synchronizer mutt(__single_stepper());
RSA_free(_key);
ssl_init::~ssl_init()
{
- FUNCDEF("dtor");
+ FUNCDEF("destructor");
LOG("prior to crypto cleanup");
CRYPTO_cleanup_all_ex_data();
#include <textual/parser_bits.h>
#include <textual/string_manipulation.h>
-//#define DEBUG_SYMBOL_TREE
+#define DEBUG_SYMBOL_TREE
// uncomment for totally noisy version.
#include <loggers/program_wide_logger.h>
#include <basis/functions.h>
#include <basis/guards.h>
-//#define DEBUG_TREE
+#define DEBUG_TREE
// uncomment if you want lots of debugging info.
#undef LOG
tree::~tree()
{
+ FUNCDEF("destructor");
// must at least unhook ourselves from the parent so we don't become a lost
// cousin.
tree *my_parent = parent();
// or there are no kids at all.
curr_node = curr_node->branch(0);
+LOG(a_sprintf("loop traverse on %p", curr_node));
+
if (curr_node == NULL_POINTER) {
// wayback has no children, so we can take action.
+LOG(a_sprintf("inside null condition, loop traverse on %p", curr_node));
// if wayback is the same as "this", then we exit from iterations since
// we've cleaned all the kids out.
#hmmm: don't fail if the hierarchy doesn't exist.
# high priority stuff would be called urgent.
-analyze_hierarchy_and_report $CLOUD_BASE/urgent "high priority (aieeee!)"
+analyze_hierarchy_and_report $CLOUD_BASE/aaa_priority "high priority (aieeee!)"
# notes are individual files of tasks, usually, although some are combined.
analyze_hierarchy_and_report $CLOUD_BASE/grunty* "grunty (external facing) notes"
analyze_by_dir_patterns "life's work and other oddities" $CLOUD_BASE/vocation*
# scan all the items declared as active projects.
-analyze_by_dir_patterns "active issues" $CLOUD_BASE/active*
+analyze_by_dir_patterns "active issues" $CLOUD_BASE/*active*
# rub alongside all the travel notes to see if any have interesting burrs.
analyze_by_dir_patterns "travel plans" $CLOUD_BASE/walkabout*
# scan across all appropriately named project or research folders.
-analyze_by_dir_patterns "running projects" $CLOUD_BASE/project* $CLOUD_BASE/research*
+analyze_by_dir_patterns "running projects" $CLOUD_BASE/*project* $CLOUD_BASE/*research*
# look for our mad scientist style efforts.
-analyze_by_dir_patterns "lab experiments" $CLOUD_BASE/experiment*
+analyze_by_dir_patterns "lab experiments" $CLOUD_BASE/*experiment*
# snag any work related items for that category.
analyze_by_dir_patterns "jobby work tasks" $CLOUD_BASE/job*