As I said before, any difference in the libs that aren't actually in use for the test don't matter.

The kernel modules could theoretically matter depending on what exactly they do. It's not very likely though unless it's one the code in question actually passes through. A slightly corrupted disk or memory subsystem can cause all kinds of random errors, some of which may be as subtle as this.

It's easy to assume that things just fail when they are not fully intact, but that's not always the case. I once diagnosed a PATA drive cable as bad over the shoulder of a hardware technician by pointing out to him that the same bits were dropping off of every n^th character in the output of a DOS dir command. Other than that sort of issue, simple programs seemed to run just fine on that system. Software corruption can be even more subtle since the problem can be in a rarely used code path.