Author: sewardj
Date: 2008-02-26 01:10:07 +0000 (Tue, 26 Feb 2008)
New Revision: 7471
Log:
Comment-only change.
Modified:
branches/DATASYMS/coregrind/m_debuginfo/readdwarf3.c
Modified: branches/DATASYMS/coregrind/m_debuginfo/readdwarf3.c
===================================================================
--- branches/DATASYMS/coregrind/m_debuginfo/readdwarf3.c 2008-02-26
01:09:37 UTC (rev 7470)
+++ branches/DATASYMS/coregrind/m_debuginfo/readdwarf3.c 2008-02-26
01:10:07 UTC (rev 7471)
@@ -105,6 +105,11 @@
whether or not they advanced the DIE cursor, and only if they
didn't should read_DIE itself read through the DIE.
+ ML_(addVar) and add_var_to_arange: quite a lot of DiAddrRanges have
+ zero variables in their .vars XArray. Rather than have an XArray
+ with zero elements (which uses 2 malloc'd blocks), allow the .vars
+ pointer to be NULL in this case.
+
More generally, reduce the amount of memory allocated and freed
while reading Dwarf3 type/variable information. Even modest (20MB)
objects cause this module to allocate and free hundreds of
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
