|
From: <sv...@va...> - 2005-09-13 21:11:19
|
Author: njn Date: 2005-09-13 22:11:12 +0100 (Tue, 13 Sep 2005) New Revision: 195 Log: Add a new project: make debug info reading incremental. Modified: trunk/devel/projects.html Modified: trunk/devel/projects.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/devel/projects.html 2005-09-13 20:29:46 UTC (rev 194) +++ trunk/devel/projects.html 2005-09-13 21:11:12 UTC (rev 195) @@ -243,6 +243,18 @@ August 27, 2005)</p> =20 =20 +<h3>Incremental debug info reading</h3> +<p>When a code segment is loaded Valgrind mmaps the entire file into +memory and reads the debug info all in one hit. If the code segment is +big (eg. 300MB) the mmap will fail and no debug info will be read for +that segment. It would be nice if the debug info reader was more +incremental. This project will require an understanding of ELF formats, +and to a lesser extent, debugging formats (DWARF, stabs). The place to +start looking is m_debuginfo/symtab.c, in the function +VG_(read_seg_symbols)(). That code is not very pretty, and could do +with a clean-up anyway. (Added September 13, 2005) + + <h3>Addrcheck and/or compressed V bit representation</h3> <p>Memcheck more than doubles the amount of memory a program uses, due to its V bits. Addrcheck only increases memory by 1/8th. However, |