[Gc] Verbose Leak Detection

Volkan YAZICI yazicivo at ttmail.com
Sun May 16 01:14:59 PDT 2010


Hi,

Using CVS tip of Boehm GC compiled with --enable-large-config flag
turned on. Just after GC_INIT(), setting GC_find_leak to 1 to enable
leak detection. Despite the whole program is compiled without any
optimization flags, Boehm GC outputs as follows:

  Leaked atomic object at start: 0x1363e7000, appr. length: 13136
  Leaked atomic object at start: 0x1363e3000, appr. length: 13136
  Leaked atomic object at start: 0x1363c9000, appr. length: 13136
  Leaked atomic object at start: 0x1363c5000, appr. length: 13136
  Leaked atomic object at start: 0x1363b1000, appr. length: 43696
  Leaked atomic object at start: 0x136391000, appr. length: 144
  Leaked atomic object at start: 0x136391090, appr. length: 144
  Leaked atomic object at start: 0x136391120, appr. length: 144

Wouldn't it be possible to make Boehm GC output more verbose debugging
information about the program itself also -- as advertised in the
website as well? For instance,

  Leaked composite object at 0x806dff0 (leak_test.c:8, sz=4)

BTW, this is an x86_64 GNU/Linux system.


Regards.


More information about the Gc mailing list