I always use Standard_GUID("MyDriver") to `uniquely' identify my driver, but sometimes I will call a wrong Function Driver and sometimes not. This is a hard-to-replay bug.
I think using Standard_GUID("MyDriverName") is a wrong method, we should use guidgen.exe to generate a copy and embed it into source.
I suspect that Standard_GUID(string) will use some hasing algorithm to generate a GUID.
But I haven't have a look at source code.( You know, as far as OCC's source if it is not too simple so do nothing except for calling another or just include XXX.ixx/XXX.jxx, it will be very complex and ugly to comprehend. :-(. )
I insist on my viewpoint because I have found an old post reported the same error. and in source code of OCAF, all GUID is hard-coded and accessed by fucntion, they never use such as Standard_GUID("TDataStd_Name").
SO I THINK SampleOCAF IS MISGUIDING.
Any idea about this problem?