lwIP - A Lightweight TCP/IP stack - Bugs: bug #33803, API message type incorrect
You are not allowed to post comments on this tracker with your current authentication level.
bug #33803: API message type incorrect
Submitter: | Brad Giffel <bgiffel> | ||
Submitted: | Tue 19 Jul 2011 08:29:46 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Duplicate |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | CVS Head |
Wed 20 Jul 2011 04:26:45 AM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Tue 19 Jul 2011 08:29:46 PM UTC, original submission:
The new functions for using static messages from interrupt handlers has a problem with the message type. When calling tcpip_callbackmsg_new() the function sets the message type to TCPIP_MSG_CALLBACK which would cause the tcpip_thread() function to free the message after the callback. This is not the intended behaviour, the message structure should not be deleted.
|
Brad Giffel <bgiffel> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-07-20 | goldsimon | Status | None | Duplicate | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-bb6a.
Corresponding source code
Duplicate to bug #33801, already fixed.