buglwIP - A Lightweight TCP/IP stack - Bugs: bug #28970, tcpip_thread bug.

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #28970: tcpip_thread bug.

Submitted by:  hanhui <hanhui03>
Submitted on:  Mon 22 Feb 2010 10:26:26 AM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: Change RequestStatus: Fixed
Privacy: PublicAssigned to: Simon Goldschmidt <goldsimon>
Open/Closed: ClosedPlanned Release: None
lwIP version: CVS Head

Mon 22 Feb 2010 12:57:18 PM UTC, comment #3:

Fixed, thanks for reporting.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Mon 22 Feb 2010 10:44:52 AM UTC, comment #2:

> Many applications have been used ETIMEDOUT error number, now
> suddenly changed to EWOULDBLOCK will have an impact on many
> applications.
> So I suggest do not often modify these places, this will cause
> a lot of applications that need to be changed


This part is easy to deal with.

If we have in the past used ETIMEDOUT where EWOULDBLOCK is correct then that is a bug and we need to fix it (as I think has been recently done). If applications have used ETIMEDOUT then they need to be fixed too. It's not a good idea to leave bugs in just because to fix them would cause incompatability. There will be lots of API changes in 1.4.0, so this is a good time to fix such problems.

We can now leave this bug open to deal with the tcpip_thread problem described.

Kieran Mansley <kieranm>
Project Administrator
Mon 22 Feb 2010 10:41:14 AM UTC, comment #1:

Hanhui: when filing bugs, please:

(i) Make sure you describe what the problem is as well as your suggested fix. It's great that you're contributing solutions but knowing what you're trying to solve helps too.

(ii) Only put one problem in each bug report, don't just use one bug report for a list of things.

This will make things much easier to deal with. Thanks!

Kieran Mansley <kieranm>
Project Administrator
Mon 22 Feb 2010 10:26:26 AM UTC, original submission:

if do not define LWIP_TCPIP_CORE_LOCKING_INPUT

tcpip_thread() can not process TCPIP_MSG_INPKT packet!

===========================================================

other request:

Many applications have been used ETIMEDOUT error number, now suddenly changed to EWOULDBLOCK will have an impact on many applications.

So I suggest do not often modify these places, this will cause a lot of applications that need to be changed

hanhui <hanhui03>

 

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 kieranm (Posted a comment)
  • -unavailable- added by hanhui03 (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
    Mon 22 Feb 2010 12:57:18 PM UTCgoldsimonStatusNone=>Fixed
      Assigned toNone=>goldsimon
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1