summaryrefslogtreecommitdiff
path: root/nuttx/TODO
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-12-20 15:48:24 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-12-20 15:48:24 +0000
commitd33c80d341f3505bb3f7e1d5977b4883ed64dbd7 (patch)
tree316d831602c9ff733fd1aa3287ef83b9a318d44e /nuttx/TODO
parent4eb8023428e87fcc9f6785ae8631b610874e708b (diff)
downloadpx4-nuttx-d33c80d341f3505bb3f7e1d5977b4883ed64dbd7.tar.gz
px4-nuttx-d33c80d341f3505bb3f7e1d5977b4883ed64dbd7.tar.bz2
px4-nuttx-d33c80d341f3505bb3f7e1d5977b4883ed64dbd7.zip
update
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2397 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/TODO')
-rw-r--r--nuttx/TODO14
1 files changed, 10 insertions, 4 deletions
diff --git a/nuttx/TODO b/nuttx/TODO
index ade6ad888..17c9767e3 100644
--- a/nuttx/TODO
+++ b/nuttx/TODO
@@ -273,8 +273,11 @@ o Network Utilities (netutils/)
when the problem goes away with debug output enabled (and also since
output from the CGI program is re-directed; you can redefine bdbg to
be lldbg in include/debug.h to get non-re-directed debug output).
- Status: Open
- Priority: High
+ Status: Open.
+ UPDATE: I have found that increasing the size of the CGI program stack
+ from 1024 to 2048 (on the LM3S) eliminates the problem. So the most
+ likely cause is probably a stack overflow, not a hard sofware bug.
+ Priority: Probably Low
Description: If the network is enabled, but THTTPD is not configured, it spews out lots
of pointless warnings. This is kind of annoying and unprofessional; needs to
@@ -680,8 +683,11 @@ o ARM/LM3S6918 (arch/arm/src/lm3s/)
Description: There are some lingering bugs in THTTPD, possibly race conditions. This
is covered above under Network Utilities, but is duplicated here
to point out that the LM3S suffers from this bug.
- Status: Open
- Priority: High
+ Status: Open.
+ UPDATE: I have found that increasing the size of the CGI program stack
+ from 1024 to 2048 (on the LM3S) eliminates the problem. So the most
+ likely cause is probably a stack overflow, not a hard sofware bug.
+ Priority: Probably Low
o ARM/STM32 (arch/arm/src/stm32/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^