Anand Avati wrote:
OK, this is getting serious.
I have just discovered that the contents of my .viminfo has somehow been
clobbered by a .pine-debug file. It almost smells like it might be a leaky
pointer stomp. This may or may not be related to bug 126.
I have also just found that some of my log files are similarly corrputed
(nvidia-installer.log seems to have parts of the syslog message log in it!).
Do you have io-cache in your config?
No, I don't use any performance translators.
Can you attach the .viminfo and .pine-debug files to bug #163?
No, sorry, I deleted them as they weren't important and it was stopping
vim from working. I presume you mean #126 - #163 is a different (but
possibly related) bug. I have, however, attached the copies of the good
and corrupted libraries to #126, which may be helpful if it is the same
bug. The corrupted library looked like it had a part of a directory
listing at the bottom (do diff of strings on them).
Gordan
