Reg add "HKCU\SOFTWARE\Cxbx-Reloaded" /v KrnlDebugFilename /t REG_SZ /d #4134-WORKING.txt /f
Start /MIN %MASTER_EXE% "C:\3925\default.xbe" Reg add "HKCU\SOFTWARE\Cxbx-Reloaded" /v KrnlDebugFilename /t REG_SZ /d #3925-master.txt /f Start /MIN %WORKING_EXE% "C:\3925\default.xbe" Reg add "HKCU\SOFTWARE\Cxbx-Reloaded" /v KrnlDebugFilename /t REG_SZ /d #3925-WORKING.txt /f SET MASTER_FOLDER=D:\git\Cxbx-Reloaded-master\build\win32\Release\ SET WORKING_FOLDER=D:\git\Cxbx-Reloaded\build\win32\Release\ Please specify the folder according to your environment. Run this batch file, logs are generating automatically. I wrote a batch file to reduce regression testing effort. HLE: * Searching HLE database for D3D8 version. HLE: 0x001A0F60 -> EmuD3DDeferredTextureState HLE: 0x001A12D0 -> EmuD3DDeferredRenderState HLE: 0x0018EA4E -> GetTimeZoneInformation_3911 (Disabled) HLE: 0x001552F0 -> XRegisterThreadNotifyRoutine_3911 HLE: * Searching HLE database for XAPILIB version. * Cxbx-Reloaded High Level Emulation database last modified Sat Mar 18 22:14:13 2017 It would be useful if the _XXXX suffix could be disregarded, then the utility would still work even if we move a signature to a different XDK. In order to easily automate this, it would be good if there was a command line parameter to Cxbx-Reloaded itself that only performs the HLE symbol scan and no other activity.Īn extract from a log file is shown below, to give an idea of what needs to be parsed. This utility should report when a symbol address differs, or when a function that was previously located is no longer found in the latest build. I was thinking we could have a simple command line utility that takes two log files outputting by Cxbx-Reloaded and compare the HLE symbol output. As it is very easy to cause regressions when editing the OOVPA data structures, it would be nice if we had some tooling we could run to find symbols which were previously matched, but are no longer matched in new builds.