Re: [lwip-users] Fw: problem in memp_alloc()

[Francois Bouchard]

I'm sorry, there is no more assertion in the current version of my program.
I reworked my initialization and it seems ok now.

The problem I have is that pbuf_alloc() always return 0x00000001, but I
begin to suspect my compiler (CodeWarrior).

Thanks

FB

----- Original Message -----
From: "Kieran Mansley" <address@hidden>
To: "Mailing list for lwIP users" <address@hidden>
Sent: Wednesday, July 01, 2009 10:59 AM
Subject: Re: [lwip-users] Fw: problem in memp_alloc()


> On Wed, 2009-07-01 at 10:41 -0400, Francois Bouchard wrote:
> > Thanks for your help.
> >
> > In my case pbuf_alloc( PBUF_RAW, pNBuf->length, PBUF_POOL) is calling
> > memp_malloc().
>
> That is odd.  Can you tell us what the value of "type" and MEMP_MAX are
> when the assertion fires?
>
> Valid memp types are controlled by lwip/memp_std.h, in a somewhat
> obscure bit of coding.  This file is imported to define, among other
> things, the enum memp_t in lwip/memp.h which in turn will set the value
> of MEMP_MAX and MEMP_PBUF_POOL.  This should ensure that MEMP_PBUF_POOL
> is < MEMP_MAX, but if the assertion is firing this is not the case and
> something very strange has happened.
>
> Kieran
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>