[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-devel] lwip_unittests crash

From: Erik Ekman
Subject: Re: [lwip-devel] lwip_unittests crash
Date: Tue, 25 Aug 2015 17:08:47 +0200

On Tue, Aug 25, 2015 at 4:59 PM, Gisle Vanem <address@hidden> wrote:
Erik Ekman wrote:

Maybe the netif_list parameter contains bad data after running the dhcp or etharp tests.

No, I'd say either the 'tcp' or 'tcp_oos' suite is broken.

Well, they seem to work for most people..
Did you try running just the tcp test? What happened?
After this diff:

--- a/test/unit/lwip_unittests.c 2015-08-24 18:54:45
+++ b/test/unit/lwip_unittests.c    2015-08-25 16:48:39
@@ -37,16 +37,25 @@
   size_t i;
   suite_getter_fn* suites[] = {
-    tcp_suite,
-    tcp_oos_suite,
+//  tcp_suite,
+//  tcp_oos_suite,
-    pbuf_suite,
+//  pbuf_suite,

And running 'lwip_unittests.exe', I get:

Running suite(s): UDP
75%: Checks: 8, Failures: 2, Errors: 0
udp/test_udp.c:52:F:UDP:test_udp_new_remove:0: Assertion 'lwip_stats.memp[MEMP_UDP_PCB].used == 1' failed
core/test_mem.c:42:F:MEM:test_mem_one:0: Assertion 'lwip_stats.mem.used >= SIZE1' failed

At least no crashes ...

If your problem with the pbuf test is that it calls LWIP_ERROR(), define that macro so that it just runs the last argument (return errorcode)
instead of asserting or whatever.

> netif_list parameter contains bad data

For sure, but where? I supposed the unit-test should detect this.
Some problem with Check or my lwip-config...

Do you run with your own lwipopts? The tests are meant to run with lwip/test/unit/lwipopts.h
I guess that is why you get igmp included, that is not enabled by default.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]