Eddie Horng: > I doubt that clang++.real has special file i/o or some signal handling that > trigger the scenario, there're many kinds of processes are running in > android building but the only busy looping process is always the same one > in all my reproducing test. BTW, the return value from " err = func(file, > buf.u, size, pos); " is -4, for your reference. I'll test the patch by Mon.
Ok, 4 is EINTR. As you gueesed, clang++ may send SIGKILL to his children(process or thread) and it may cause the problem. I'm looking forward to read your report. Thanx J. R. Okajima ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
