TYPO3 Core

Here comes the backtrace file.

Do you by chance have TCA for your mm-table defined? The code in DatabaseIntegrityCheck->lostRecords() has a check for ctrl/label, implying this is defined in your TCA, but not in your ext_tables.sql:

if (!empty($GLOBALS['TCA'][$table]['ctrl']['label'])) {
    $selectFields[] = $GLOBALS['TCA'][$table]['ctrl']['label'];
}

Hey.

So this was a bug in the extension.

I don't agree to your claim "the TYPO3 code for DB check should raise an exception about the real error that the 'title' field is not in the TCA and not in the ext_tables.sql", though:
TYPO3 takes TCA definitions as granted at many places throughout the core. The system in general does not check for existence of DB fields before querying them. At least not at runtime. The DatabaseIntegrityCheck should not be an exception here.

We could potentially create some checker - for instance in the install tool - that looks for integrity issues between TCA definitions and DB field existence in general, but I fear that wouldn't help that much, considering the fact that core already auto-creates tons of DB fields even without having a definition in ext_tables.sql already. I'd say your case is rather edgy - so edgy that you bug was within your extension for probably quite some time already, which makes such a core functionality even more questionable. Also, the backtrace revealed your configuration error quite quickly, the combination of "'title' column queried, plus backtrace" is pretty clear.

As such, I'll reject the issue for now, and will not create a new issue for a potential 'checker' since that feature would imho be quite limited in its usefulness.