[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #55513] Uninitialized variable in struct netconn
From: |
Dirk Ziegelmeier |
Subject: |
[lwip-devel] [bug #55513] Uninitialized variable in struct netconn |
Date: |
Fri, 18 Jan 2019 14:49:44 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
URL:
<https://savannah.nongnu.org/bugs/?55513>
Summary: Uninitialized variable in struct netconn
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: dziegel
Submitted on: Fri 18 Jan 2019 07:49:42 PM UTC
Category: sockets/netconn
Severity: 3 - Normal
Item Group: Faulty Behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
lwIP version: git head
_______________________________________________________
Details:
Reported via email:
Karol Domagalski address@hidden via srs2.kundenserver.de
5:04 PM (3 hours ago)
to lwip-devel
Dear LwIP developers
My program stucks in busy loop in the netconn_mark_mbox_invalid function (in
the src/api/api_msg.c file). This is because conn->mbox_threads_waiting is set
to random value. This problem only appears if MEMP_MEM_MALLOC is set 1 (in
lwipopts.h file).
As I can see conn->mbox_threads_waiting is never initiated to known value.
After adding this in the netconn_alloc function :
#if LWIP_NETCONN_FULLDUPLEX
conn->mbox_threads_waiting = 0;
#endif
Problem seems to be solved.
The problem does not appear when MEMP_MEM_MALLOC is set to 0 because the
memory pools are used instead of the heap. Typically, each system sets these
pools to zero during startup.
Regards
--
Karol Domagalski
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?55513>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
- [lwip-devel] [bug #55513] Uninitialized variable in struct netconn,
Dirk Ziegelmeier <=