- summary: possible bug in <record> for windows --> possible bug in record for windows</record>
following log by roland nygren suggests a possible bug
in the record-handling for windows:
Feb 26
14:14:07.35|TUCPU=140|TKCPU=78|-1|60001|CC|CC:[INFO
] Recording:
*c:\publicVoiceXML/recordings/20040226_141406PM_incredibly_important_message_0.wav*Feb
26
14:14:07.35|TUCPU=140|TKCPU=78|0|8000||GrammarManager::InternalRecognize-
VXIrecInterface::Recognize returned status
-842150451Feb 26
14:14:07.35|TUCPU=140|TKCPU=78|0|com.yourcompany.vxi|420|message=function
returned an invalid VXIrecStatus codeFeb 26
14:14:07.35|TUCPU=140|TKCPU=78|-1|60001|CC|CC:[DEBUG
] Searching for line with VXI-Channel-No 0x0Feb 26
14:14:07.35|TUCPU=140|TKCPU=78|-1|60001|CC|CC:[DEBUG
] Line foundAssertion failed: "VXItrdMutexLock( ) on
already locked mutex" == NULL, file
c:\publicvoicexml\src\trd\osbtrdwin32.cpp, line
201abnormal program termination