Re: [lwip-devel] pbuf_chain followed by pbuf_free

[Jani Monoses]

> >
> I did not mean: how many times does it occur in the code. It meant:
> How many times are the instances in the code called upon, in a running
> programming.

On every tcp segment enqueued with the nocopy flag and once more in
tcp_out if there's place on the unsent queue. Then once in tcp_in if
OOSEQ is used and several places in ppp.

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

Jani