A real edge case here:

Was trying to re-wrap a DCP created with Fraunhofer easyDCP Creator+ Version 1.4.2 in DCP-o-matic.

This DCP has 3 extraneous MXF files listed in the Assetmap which aren't referenced in either the PKL or CPL. All 3 files are empty (0 bytes length).

When trying to open this DCP in DCP-o-matic, it fails with:

Programming error at ../src/dcp.cc:214

I manually edited the Assetmap file to remove the references to these 3 empty files, and then DCP-o-matic opens it happily.

This DCP is clearly very strangely made - why reference files in Assetmap which aren't used in the actual compositions? And why include 0 byte-length files? But nonetheless, dcp_inspect says it's a valid DCP (except for an unrelated schema check failure). So I would have expected DCP-o-matic to open it successfully.