Bug#178790: gcc sig11 - no longer reproduced, hardware problem?
Today (2 reboots down the road), the very same cmdline in the
very same place (although untarred again into a different directory)
goes flawlessly. I am sorry to not have applied the sig11 FAQ
techniques on the spot during the original submission.
(I'm talking about http://www.tldp.org/FAQ/sig11/html/index.html )
What mislead me was that originally I tried the compilation several
times (with cleaning the whole tree, or just on the spot),
and it ALWAYS stopped on the same file. But the FAQ explains this
- I should have forced the gcc tools and the sources out of the cache
before the recompilation, which I haven't done.
The reason that I got back to it is that another bug (Bug #181153,
which I now CC to as well) raised a strong suspicion of the maintainer
that I might have a hardware problem, so I got back to revising
all the bugs filed from this machine. Coincidence of 2 bugs with
a strong possibility of a hardware problem is very suspicious.
I'll subject the machine to severe checks and will report if any
new stuff surfaces. Right now it has 6 days uptime w/o any problems
since the last reboot (the reboot was from the OOPS in Bug #181153).
/me LARTing myself heavily on the head
Sorry for having wasted your time in the (most likely) case it's a
hardware problem on my end.
Vassilii
Reply to: