lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] LWIP_ASSERT("pbuf_free: p->ref > 0", p->ref > 0);


From: Mumtaz Ahmad
Subject: Re: [lwip-users] LWIP_ASSERT("pbuf_free: p->ref > 0", p->ref > 0);
Date: Fri, 22 Sep 2006 09:21:04 +0500

Kieran

I exactly did this and last night i got the same problem in single
connection as well ,though after 3 GB of data transfer .
However i will confirm my locking mechanism and try to debug it.

Regards


----- Original Message ----- 
From: "Kieran Mansley" <address@hidden>
To: "Mailing list for lwIP users" <address@hidden>
Sent: Friday, September 22, 2006 12:18 AM
Subject: Re: [lwip-users] LWIP_ASSERT("pbuf_free: p->ref > 0", p->ref > 0);


> On Thu, Sep 21, 2006 at 03:14:51PM +0500, Mumtaz Ahmad wrote:
> > Dear all
> >
> > When i use multiple threads sending on 2 different sockets i sometimes
get
> > this assert
> > LWIP_ASSERT("pbuf_free: p->ref > 0", p->ref > 0);
> > I have tried to make the stack thread safe . Any body who could comment?
>
> I think it is most likely that you've missed something with regards to
> making it thread safe.  You could try something really simple that
> should definitely work, such as having a single lock that controls
> access to the stack, and anything calling any part of the stack must
> first acquire this lock.  I think things passing packets up from above
> as well as calls from the application would need to be protected in
> this way.
>
> Kieran
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>
> -- 
> This message has been scanned for viruses and
> dangerous content by Streaming Networks, and is
> believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by Streaming Networks, and is
believed to be clean.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]