Major league corruption - anyone seen anything like this?

[Skip Montanaro]

    >> I realized that might be an issue on my way home.  This is on my
    >> development machine.  I (user == skip) do have write access to
    >> /usr/local/*.  Sorry about the missing info.

    Fernando> - what filesystem are you using?

ext2.

    Fernando> - are all the files which get corrupted files that get
    Fernando> explicitly open by your crashing process?

It appears so.  As far as I could tell, all the .so files that were writable
by me and dlopened by the Python interpreter got zapped.  That included the
gcc 3.0.1 .so file, readline.so, etc, but not libc.

    Fernando> [ tale of reboot woe elided ].  I give you this background in
    Fernando> case you can spot some similarities with your situation.

Thanks, but that doesn't ring any bells.

Oh well, I'll launch myself back into the fray tomorrow and see if I can
figure anything else out.

Skip