I am stumbling over this:
In a module (currently against the 3.15 branch on Debian Linux) I have defined a local record type. What I am seeing:
If the first record instance that my IOC loads is of that new record type, the database gets corrupted.
The IOC commands (dbl, dbDumpRecord) show a fake bi record that either has a weird name (arbitrary bytes), shows "(null)" or an empty string. Almost every time, the IOC segfaults while doing the 'dbl' or 'dbDumpRecord'. Stray pointer, obviously.
As soon as the first record being loaded is not an instance of my locally defined type, everything is fine.
I will certainly dive in and find what's causing this, but if someone has seen this before, I would appreciate a heads-up to shorten that procedure.
Thanks a lot,
~Ralph
