sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix potential memory leak

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3312 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2011-02-23 12:09:09 +00:00
parent 7ff5349649
commit 5e523ebd93
3 changed files with 11 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1463,9 +1463,8 @@
a USB host HID keyboard configuraion. a USB host HID keyboard configuraion.
* drivers/usbhost/hid_parser.c -- Leverages the LUFA HID parser written by * drivers/usbhost/hid_parser.c -- Leverages the LUFA HID parser written by
Dean Camera. Dean Camera.
* lib/lib_getopt() -- Correct an error in the getopt() logic: On certain error * examples/nsh -- Correct an usage of getopt(): If you stop calling getopt()
return cases, the state was not being reset correcly and incorrect behaviors before all parameters are parsed, you can leave getopt() in a strange state.
could occur on subsequent calls to getopt().

5
Documentation/NuttX.html
View File

@ -2040,9 +2040,8 @@ nuttx-5.18 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>
a USB host HID keyboard configuraion. a USB host HID keyboard configuraion.
* drivers/usbhost/hid_parser.c -- Leverages the LUFA HID parser written by * drivers/usbhost/hid_parser.c -- Leverages the LUFA HID parser written by
Dean Camera. Dean Camera.
* lib/lib_getopt() -- Correct an error in the getopt() logic: On certain error * examples/nsh -- Correct an usage of getopt(): If you stop calling getopt()
return cases, the state was not being reset correcly and incorrect behaviors before all parameters are parsed, you can leave getopt() in a strange state.
could occur on subsequent calls to getopt().
pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>

21
TODO
View File

@ -1,4 +1,4 @@
NuttX TODO List (Last updated January 26, 2011) NuttX TODO List (Last updated February 11, 2011)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(5) Task/Scheduler (sched/) (5) Task/Scheduler (sched/)
@ -24,7 +24,7 @@ NuttX TODO List (Last updated January 26, 2011)
(1) ARM/C5471 (arch/arm/src/c5471/) (1) ARM/C5471 (arch/arm/src/c5471/)
(3) ARM/DM320 (arch/arm/src/dm320/) (3) ARM/DM320 (arch/arm/src/dm320/)
(2) ARM/i.MX (arch/arm/src/imx/) (2) ARM/i.MX (arch/arm/src/imx/)
(4) ARM/LPC17xx (arch/arm/src/lpc17xx/) (3) ARM/LPC17xx (arch/arm/src/lpc17xx/)
(7) ARM/LPC214x (arch/arm/src/lpc214x/) (7) ARM/LPC214x (arch/arm/src/lpc214x/)
(2) ARM/LPC313x (arch/arm/src/lpc313x/) (2) ARM/LPC313x (arch/arm/src/lpc313x/)
(3) ARM/STR71x (arch/arm/src/str71x/) (3) ARM/STR71x (arch/arm/src/str71x/)
@ -684,13 +684,6 @@ o ARM/i.MX (arch/arm/src/imx/)
o ARM/LPC17xx (arch/arm/src/lpc17xx/) o ARM/LPC17xx (arch/arm/src/lpc17xx/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description: If debug is enabled so that there is a lot of early serial console output,
The serial console output may be garbled initially. If this becomes a
problem during debug, I've found that just putting a delaying at the
beginning of os_start() (sched/os_start.c) eliminates the garbled output.
Status: Open
Priority: Low, only effects debug and there is a workaround
Description: USB DMA not fully implemented. Partial logic is in place but it is Description: USB DMA not fully implemented. Partial logic is in place but it is
fragmentary and bogus. (Leveraged from the lpc214x) fragmentary and bogus. (Leveraged from the lpc214x)
Status: Open Status: Open
@ -754,11 +747,11 @@ o ARM/LPC214x (arch/arm/src/lpc214x/)
Status: Open Status: Open
Priority: Uncertain Priority: Uncertain
Description: Possible errors in USB device driver reported "I suspect there’s a few Description: Possible errors in USB device driver reported "I suspect there's a few
issues in the lpc214x USB driver – in particular it doesn’t stall both issues in the lpc214x USB driver - in particular it doesn't stall both
in/out endpoints for unsupported setup requests and it doesn’t call in/out endpoints for unsupported setup requests and it doesn't call
CLASS_DISCONNCET on a USB reset – I don’t have any access to that hardware CLASS_DISCONNCET on a USB reset - I don't have any access to that hardware
so can’t pursue it really." so can't pursue it really."
Status: Open Status: Open
Priority: Medium Priority: Medium