Comment #2 on issue 3452 by ya...@rogers.com: GlorpDBX no longer loads due to garbled timestamp http://code.google.com/p/pharo/issues/detail?id=3452 Filed-in the 2 changesets in Issue 3224, and got the same stack trace as before. Today, I figured that maybe the timestamp is not garbled, an really is: pm From VisualWorksÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂ...etc... I changed #parseTimestampFrom: to check for 'VisualWorks' (see attached change set). Here are the crucial lines: ^ ((aString isEmpty or: [aString includesSubString: 'VisualWorks']) or:[aString = '<historical>']) ifTrue:[DateAndTime new] ifFalse:[ "Get the date start index and extract only those tokens that represent date or time" ... Now everything loaded fine. Attachments: SourceReference-parseTimestampFrom.st 1.3 KB