Bug#38998: libc6 2.1.1-10 causes programs to SIGILL on 386sx/16
To create a broken system, follow these steps:
1. Acquire a 386sx/16 (though i think any 386sx would do)
2. Install the slink base system (works great)
3. Attempt to upgrade the system, via `apt-get dist-upgrade', to potato
Step three will get as far as unpacking libc6 (2.1.1-10), and will then try
to run the post-install script, which dies with error 132. This is due to `date'
exiting with an illegal instruction. (I only had the base system installed,
and not gdb, so I can't say much more than that.) The groff package also started
SIGILL'ing on me, as well as `ls -l' (though curiously, not plain `ls').
Perhaps the latest libc was accidentally compiled with -m486? Or maybe the latest
gcc hasn't been fully tested on ancient machines.
-- System Information
Debian Release: potato
Kernel: Linux bernice 2.2.9 #2 Fri Apr 16 18:58:40 EST 1999 i386
Versions of packages libc6 depends on:
ii ldso 1.9.11-2 The Linux dynamic linker, library and utilit