[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX] Text corruption

From: David Kastrup
Subject: Re: [AUCTeX] Text corruption
Date: Mon, 17 Dec 2012 00:32:38 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

"Axel E. Retif" <address@hidden> writes:

> David,
> On 12/16/2012 02:44 PM, David Kastrup wrote:
>> Tassilo Horn <address@hidden> writes:
> [...]
>>> That's a really strange problem.  It doesn't sound like an Emacs or
>>> AUCTeX problem but more like a colleague playing a trick on you.
>> More like the computer playing a trick on him.  i (0x69) and m (0x6d)
>> differ by a single bit, bit 2.  Time to run some memory checker.
> I ran memtester for about an hour, without any problem.

I've had this more than once: different CPU generations and chipsets,
nothing to be seen under regular memtest.  It might be related to some
memory accesses (like opcode fetches) being affected more by timing
problems than others, or it might be partly a refresh problem that just
does not emerge in the quasi-regular patterns from a memory test.

But program errors (and/or a bad bit in program code or address) are not
likely to accidentally cause merely a single bit change.  While the
"evidence" so far is minuscule, my current guess would be bad memory.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]