RE: Added test script

From: [email protected]
[mailto:[email protected]] On Behalf Of David Griswold
Sent: Monday, May 07, 2007 7:10 AM
To: strongtalk
Subject: Added test script

We need a large deterministic system test that can be run from the command
line, in order to progress with VM debugging. I've used the new script
facility for that purpose.

The new system test is run by executing the new batch file "tools\test.bat"
from the Strongtalk home directory.  It not only runs all the unit tests for
the libraries, but also recompiles all the methods in the system (using the
bytecode compiler, which is written in Smalltalk), which takes quite a
while.

Recompiling all methods had not worked up till now; that is now fixed, at
least under the UI.  The main problem was that the Strongtalk source
database was corrupted because there were both a class named Point and POINT
(the name of a Win32 structure), which didn't cause a problem in Strongtalk
because it is case sensitive, but corrupted the source database because the
indices are stored in folders named by the class and Windows isn't
case-sensitive.

Recompiling all methods from the UI works in interpreted-only mode, but
crashes the VM when run from the test script.  This gives us a good place to
start debugging.  Also, recompiling all methods failed even under the UI in
compiled mode, but let's start with the interpreter.

To run the new test script, you will need to:
• checkout tools\{test.dlt, test.bat, strongtalkrc-forInterpretedTests}
• checkout and filein StrongtalkSource\{WinPOINT.dlt,  MINMAXINFO.dlt,
Win32Control.dlt, Window.dlt, SystemInitializer.dlt}
• checkout vm\runtime\arguments.cpp and recompile.
Dave



Greetings,

> • checkout vm\runtime\arguments.cpp and recompile.	

	Step 1.

	Done. New Strongtalk_debug.exe was built with VS8 SP1 under Vista
X64.

> • checkout and filein StrongtalkSource\{WinPOINT.dlt,  MINMAXINFO.dlt,
Win32Control.dlt, Window.dlt, SystemInitializer.dlt}

	Step 2.

	Is this step necessary if the new strongtalk.bst (checked out) is
used ?

	The Strongtalk launcher seems to hang after complaining:
	
		"identifier expected"

	when WinPOINT.dlt was filed in 
	(newly checked out strongtalk.bst, newly built
strongtalk.exe/strongtalk_debug.exe 
	under Vista Enterprise x64 and Windows 2003 TSE x86).

	Could anyone successfully pass step 2?

> • checkout tools\{test.dlt, test.bat, strongtalkrc-forInterpretedTests}


	Regards,

	PhiHo

	P.S: The whole strongtalk trunk at revision 94 was checked out.
		incls folder was stolen from "strongtalk r36-noasm2 VM pack"
		with a commented out line from _interpreter.cpp.incl:

		// # include "generatedPrimitives.hpp"



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---