Menu ▾ ▴

#4 Memory issue debugging patch

1.0
closed
None
2015-03-14
2015-03-09
Chad Woolf
No

I found making this change to be very useful for debugging memory issues. For debugging purposes it routes everything through genalloc/genfree instead of using the memory table structure. This enables platform tools on OS X to be able to find memory related issues more easily. Scribble, guard malloc, and clang's address sanitizer are a lot more useful.

During a debug build, all you have to do is define MEM_TABLE_SIZE to be zero, and you get the alternate set of macros.

I've included the patch if you find it useful.

1 Attachments

Discussion

  • Gary Riley

    Gary Riley - 2015-03-14

    Great idea. Changes checked in as r253 and several issues fixed after using scribble and guard malloc checked in as r254.

     
  • Gary Riley

    Gary Riley - 2015-03-14
    • status: new --> closed
    • assigned_to: Gary Riley
     

Log in to post a comment.