buglwIP - 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

Submitted by:  Brad Giffel <bgiffel>
Submitted on:  Tue 19 Jul 2011 08:29:46 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: Faulty BehaviourStatus: Duplicate
Privacy: PublicAssigned to: Simon Goldschmidt <goldsimon>
Open/Closed: ClosedPlanned Release: None
lwIP version: CVS Head

Wed 20 Jul 2011 04:26:45 AM UTC, comment #1:

Duplicate to bug #33801, already fixed.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
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.

Line 419 in tcpip.c should be:

msg->type = TCPIP_MSG_CALLBACK_STATIC;

Brad Giffel <bgiffel>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by goldsimon (Posted a comment)
  • -unavailable- added by bgiffel (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 20 Jul 2011 04:26:45 AM UTCgoldsimonStatusNone=>Duplicate
      Assigned toNone=>goldsimon
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1