Well, I'm not trying to get paid for helping here ;^)
I noticed
mem_ptr_t)name) % 4) == 0))
in both macros, so sockets.c is actually expecting the 'name' pointer to
be aligned to 32-bit boundaries.
I don't see why and I'm not familiar with lwIP's socket interface, but
this to me seems to
Thanks for your answer.
Sorry, it's an LWIP_ERROR not a LWIP_ASSERT.
I found this in sockets.c line
420
/* check size, familiy and alignment of 'name' */
LWIP_ERROR(lwip_bind: invalid address, ((namelen == sizeof(struct
sockaddr_in))
((name-sa_family) == AF_INET)
Hi
When updating lwip from 1.3.2 to 1.4.1 I see some asserts checking for
alignment equal 4. They are hard coded.
Does this mean lwip can only be used with MEM_ALIGNMENT equal 4 from this
Release on?
Regards Thomas
___
lwip-users mailing list
tm...@web.de wrote:
When updating lwip from 1.3.2 to 1.4.1 I see some asserts checking for
alignment equal 4. They are hard coded.
Does this mean lwip can only be used with MEM_ALIGNMENT equal 4 from this
Release on?
No.
You might get a more detailed answer by telling us exactly which
