connect to SMem DB in init CLI command

Previously a simple

smem --init
smem --clear

at the beginning of a source file would fail and prevent the rest of the file
from sourcing. Connect to the DB in the init CLI command so that any following
actions can access the DB. I believe this is the intuitive behavior, and I don't
see anything in the manual that would indicate that this incorrect.

.gitignore

@@ -252,7 +252,7 @@ compile_commands.json
 
 # NUNIT
 *.VisualState.xml
-TestResult.xml
+TestResults.xml
 
 # Build Results of an ATL Project
 [Dd]ebugPS/

Core/CLI/src/cli_smem.cpp

@@ -133,9 +133,11 @@ bool CommandLineInterface::DoSMem(const char pOp, const std::string* pArg1, cons
     }
     else if (pOp == 'i')
     {
-        /* Don't think we need clear out anything else any more */
-
-        thisAgent->SMem->reinit();
+        if (thisAgent->SMem->connected()) {
+            thisAgent->SMem->reinit();
+        } else {
+            thisAgent->SMem->attach();
+        }
 
         PrintCLIMessage("Semantic memory system re-initialized.");
         if (thisAgent->SMem->settings->append_db->get_value() == on)

UnitTests/SoarUnitTests/MiscTests.cpp

@@ -285,6 +285,13 @@ void MiscTests::testWrongAgentWmeFunctions()
 
 }
 
+void MiscTests::testRegression370()
+{
+	source("testRegression370.soar");
+	agent->RunSelf(5000);
+	SoarHelper::init_check_to_find_refcount_leaks(agent);
+}
+
 void MiscTests::testRHSRand()
 {
 	kernel->AddRhsFunction("failed", Handlers::MyRhsFunctionFailureHandler, 0) ;

UnitTests/SoarUnitTests/MiscTests.hpp

@@ -33,6 +33,8 @@ class MiscTests : public FunctionalTestHarness
 
 	TEST(testWrongAgentWmeFunctions, -1)
 	void testWrongAgentWmeFunctions();
+	TEST(testRegression370, -1)
+	void testRegression370();
 	TEST(testRHSRand, -1)
 	void testRHSRand();
 	TEST(testMultipleKernels, -1)