[lwip-devel] [bug #62160] MEM_OVERFLOW_CHECK, MEM_STATS_DISPLAY and mem_trim

[Jonathan D]

URL:
  <https://savannah.nongnu.org/bugs/?62160>

                 Summary: MEM_OVERFLOW_CHECK, MEM_STATS_DISPLAY and mem_trim
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: jona
            Submitted on: Wed 09 Mar 2022 02:03:38 PM UTC
                Category: None
                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: 2.1.2

    _______________________________________________________

Details:

When MEM_OVERFLOW_CHECK is activated, the "used" memory provided by
MEM_STATS_DISPLAY increased every time the "mem_trim" is called (by 32 bytes
at a time, MEM_SANITY_REGION_BEFORE and _AFTER are both 16 bytes).
The "used" memory remains constant when MEM_OVERFLOW_CHECK is deactivated.

I though at first that there was a memory leak in my code but now, I'm more
into thinking that the issue is in MEM_STATS although I didn't spot exactly
what is wrong.




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?62160>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/