<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 28, 2013, at 5:03 PM, Martin Ward wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Did add ulimit -s 32768 before testing though, and disabled those pesky mudflap test which have failed in the same place for ages.<br><br><br>Martin</span></blockquote></div><br><div>Hello Martin,</div><div><br></div><div>Thinking about adding this to the book. Although we set it before the test. Should we set ulimit back to the old setting after the test.</div><div><br></div><div>Perhaps get the ulimit stack value in a variable then set it, then unset it with th evariable and unset the variable maybe:</div><div><br></div><div>STACK=`ulimit -s`</div><div>ulimit -s 32768</div><div><br></div><div><do tests here></div><div><br></div><div>ulimit -s ${STACK}</div><div><br></div><div><br></div><div><br></div><div><br></div><div>Or is it okay to leave the stack size that huge for the remainder of the build?</div><div><br></div><div><br></div><div>Or is there a way to set the stack size without ulimit during the test phase, such as a variable somewhere?</div><div><br></div><div>SIncerely,</div><div><br></div><div>William Harrington</div></body></html>