On Thu, 2007-06-14 at 11:22 -0700, Luck, Tony wrote: > > > Interesting. If you're exceeding your stack ulimit, you should be > > > seeing either an "argument list too long" message or getting a > > > SIGSEGV. Have you tried bypassing wc and piping the output straight > > > to a file? > > > > I think it sends SIGKILL on failure paths. > > Setting stack limit to unlimited I managed to exec with 10MB, and > "wc" produced the correct output when it (finally) ran, so no > odd limits being hit in there.
Ah, good :-) > Ah ... running the 34*100K case direct from my shell prompt, I > do see a "Killed" that must get lost when I run this in the > shell script loop. Yes, so it seems we just trip the stack limit after we cross the point of no return. I started looking into growing the stack beforehand and perhaps shrinking the stack after we're done. That would get most if not all these failures before the point of no return. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/