A big, hard-coded stack size was used in several places

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@1986 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2009-07-14 01:48:06 +00:00
parent 7cee7e3f70
commit 982b40abe7

View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4"> <tr align="center" bgcolor="#e4e4e4">
<td> <td>
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1> <h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
<p>Last Updated: July 12, 2009</p> <p>Last Updated: July 13, 2009</p>
</td> </td>
</tr> </tr>
</table> </table>
@ -1489,6 +1489,10 @@ nuttx-0.4.10 2009-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;
with more standard exec() functions, however, because (1) it returns with more standard exec() functions, however, because (1) it returns
and (2) it requires symbol table arguments. and (2) it requires symbol table arguments.
* lib/: Add fileno() * lib/: Add fileno()
* examples/ostest: Several of the tests used a big, hard-coded stack size
when creating test threads (16Kb stacksize). The stack size should
be controlled by the .config file or the OSTest won't work on platforms
with memory constraints.
nuttx-0.4.10 2009-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt; nuttx-0.4.10 2009-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;