Alan Cox wrote:
On Tue, Aug 16, 2005 at 09:28:29PM +0200, Hans Verkuil wrote:
If it "just works" the second time, something is probably wrong with
your hardware. :) Run memtest86+.
Definitely not, any wild pointer or memory overwrite can give such behavior.
I've both programmed and fixed my share of these...
Generally speaking gcc or ld runs that work the second time but not the first
are hardware problems. You are feeding the same inputs to the same program
so its very unlikely (but not impossible) that it would fail once and work
the other.
gcc is particularly good for finding such things because it gives the CPU
a good hammering. Equally if it does it repeatably in the same place its
going to be a software bug.
The only variance I've seen to this is when you're doing -j4, etc. Badly
designed parallel makes can go very wierd.
Cheers,
Allan.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
