[lwip-users] arp failure results in newEntry != NULL assertion
From:
Thomas Taranowski
Subject:
[lwip-users] arp failure results in newEntry != NULL assertion
Date:
Fri, 9 Nov 2007 14:48:41 -0800
I'm able to readily reproduce the following, and am wondering if other folks have seen similar behavior, or if it's just a problem with my port.
On my target running lwIP, I while(1) sendto() to a non-existent target on the ***LOCAL*** subnet.
Result: newEntry!=NULL assertion from etharp.c. lwIP failed to allocate a memp so that it could cache the outgoing packet. Shouldn't really be an assertion, as there needs to be error handling code in place for that, but that's another issue.
On my target running lwIP, I while(1) sendto() to a non-existent target on a ***REMOTE*** subnet. Result: code works fine