Re: [lwip-devel] pbuf_chain followed by pbuf_free

[Leon Woestenberg]

Hello Jani,

> > > Could you explain this? How is he forced not to reference tail? tail
> > > is not set to NULL, it is still a valid pbuf with a refcount of at
> > > least 1.
> > >
> > The same as with the free(p) call in the C library, the programmer is
> > aware that the p pointer should no longer be referenced afterwards.
> 
> But our pbuf can and is referenced. It's more like a GC system not like
> malloc/free.
> 
Maybe that is our misunderstanding. Yes, our pbuf implementation is
exactly like a GC system, *BUT* with the difference that the programmer
is responsible for no longer referencing the pbuf that has been
pbuf_free()d.

Leon.

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++