On Feb 18, 2008 1:20 PM, Andrew Haley <aph@xxxxxxxxxx> wrote: > Sunzir Deepur wrote: > > On Feb 18, 2008 12:53 PM, Andrew Haley <aph@xxxxxxxxxx> wrote: > >> Sunzir Deepur wrote: > > >>> Have you ever heard of such gcc hanging ? Do you have any suggestion as to > >>> what can I check ? > >> Run gcc under strace -f. > > > > Great idea (wasn't aware of the -f switch) - thank you (i now have to wait > > for the problem to raise its ugly head again, it doesn't always happen) > > Right, so it really does look like an intermittent hardware problem. I really don't know. Once this shows up, it is consistent - it will not disappear until I let the compilation process to complete (which means waiting a very long period of time) for the very specific file I was trying to compile.. After I wait enough time, and the file compiles ok, I can then recompile it again and again (actually tried it in a bash while loop) and it doesn't show up again.. If that was a hardware problem, I would expect that it will go away without waiting for the compilation to succeed, just by compiling again 1 minute later.. It just looks like a weird deadlock or race condition, maybe related to the filesystem. But my feeling may be totally wrong and it may end up as a disk prob. I will report to you about my results. > > The other thing you might like to investigate is smartd. > > Let us know if you ever find out what the real cause was. Sure. Thank you very much Sunzir > > Andrew. >
