#29 Heap demaged in debug environment after free

closed-accepted
nobody
None
5
2013-03-01
2009-12-01
Anonymous
No

If defined DEBUGNAMES the free function is global (!) overloaded by a macro.
The macro "free" call free first and write then into pointer.
In a threading environment is this fatal.

Discussion

  • Steven Schweda
    Steven Schweda
    2013-03-01

    I see no positive value in the code enabled by DEBUGNAMES (Zip,
    zip.h, util.c). Until someone removes it, I would avoid it. Perhaps
    someday, someone will add some useful code for malloc()+free()
    debugging.

     
  • Steven Schweda
    Steven Schweda
    2013-03-01

    • status: open --> closed-accepted