linux-kernel - Bug? Older 32 bit program (CivCTP) no longer works under 64 bit kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <537568B5.9060208@gmail.com>
Date:	Thu, 15 May 2014 20:24:05 -0500
From:	David Hagood <david.hagood@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Bug? Older 32 bit program (CivCTP) no longer works under 64 bit kernel

I have an old native Linux 32 bit copy of Civilization: Call to Power. 
It used to work under a 64 bit environment back in the 3.0.x days. 
However, under recent versions (>3.5) it no longer runs - it complains 
that it cannot find certain files in the directory. The exact same code 
will run just fine under a 32 bit version of 3.11. I have a Pentium II 
as well as the Core 2 Duo, both running Ubuntu 14.04, same version of 
the kernel other than one is 32 bit and one is 64 bit. I've copied the 
files over from the 32 bit machine, where it runs, to the 64 bit 
machine, where it does not. I've even gone so far as to copy all the 
system 32 bit libraries into the CivCTP directory, and forced the 
program to use them (including using the ld-linux.so loader from that 
directory) - so in theory it's all the same user space libraries running 
- the only difference that I can see is that one kernel is 64 bit and 
one is 32 bit.

Running strace on the program shows that the directories being searched 
for game assets are corrupted:

16218 stat64("/home/wowbaggr/CivCTP/ctdata/englisish/uidata/keymap.txt", 
  <unfinished ...>

Note the "englisish" rather than "english".

I'm looking for any suggestions on where to look for what might cause 
such an issue - what can I do to start tracking this down.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/