how can a bit be off in memory?

Vim started crashing on me, particularly when I tried to open new lines.
I finally checked it out with rpm and a newly downloaded copy of vim's
rpm and discovered that exactly one byte, deep into vim, was wrong.

I rebooted my machine (which has been super-solid for years) - and the
difference was gone.

So, what are the opinions - did I run into a hardware glich, or was
there a freaky issue with memory mapping?

.

Relevant Pages

  • Re: how can a bit be off in memory?
    ... Vim started crashing on me, particularly when I tried to open new lines. ... I finally checked it out with rpm and a newly downloaded copy of vim's ... Are your memory DIMMS snug in their slots? ...
    (comp.os.linux.misc)
  • Re: [opensuse] vim rpm
    ... > Does anyone know where I might be able to get a regular rpm or at ... > least a spec file for vim that doesn't hassle with splitting it into ... separate components, vim, gvim, and vim-enhanced. ...
    (SuSE)
  • Re: Fedora 7 Update: vim-7.1.12-1.fc7
    ... Fedora 7 Update: vim-7.1.12-1.fc7 ... I used rpm -q vim to see which version I already have and was very ... So, when I see there's an update to "vim", my code does an rpm -q vim to ... package, ...
    (Fedora)
  • Re: [opensuse] a good small font for developing with gvim?
    ... source when I cannot find appropriate rpm or if I am tired of trying to ... Future rpm installs may cause problems with your vim install and may ... packages inherited from Debian) and make sure newbies finds them easily. ...
    (SuSE)
  • Re: vim 7.0
    ... houghi wrote: ... confusing when I did a rpm -Uvh that the old one was not overwritten. ... The old vim will still be installed and vi will still be ... You've gotta tell them. ...
    (alt.os.linux.suse)
Quantcast