Steps that may be problematic:
1) load a previously serialized CIL file using
2) do some analysis that involves makeVarinfo or
the varinfo ids and compinfo ckeys of the fresh objects
can clash w/ those in the loaded file.
Logged In: YES
Thanks for the bug report.
I have partially fixed this in the next release, by restoring nextGlobalVID and nextCompinfoKey based on values stored in the binary file. Therefore, loadBinaryFile should only be used first thing in the CIL process, before any calls to makeVarinfo or mkCompinfo. A more general solution would change the ids in the loaded file to avoid conflicts with existing varinfos and compinfos.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.