|
From: <sv...@va...> - 2006-05-01 01:49:30
|
Author: weidendo Date: 2006-05-01 02:49:28 +0100 (Mon, 01 May 2006) New Revision: 5871 Log: Hint to better run with option "--pop-on-jump" when doing self-hosting runs with outer callgrind. Modified: trunk/README_DEVELOPERS Modified: trunk/README_DEVELOPERS =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/README_DEVELOPERS 2006-05-01 01:38:32 UTC (rev 5870) +++ trunk/README_DEVELOPERS 2006-05-01 01:49:28 UTC (rev 5871) @@ -96,7 +96,10 @@ so Memcheck is not as useful as it could be. It also has not been teste= d much, so don't be surprised if you hit problems. =20 +When using self-hosting with an outer callgrind tool, use '--pop-on-jump= ' +(on the outer). Otherwise, callgrind has much higher memory requirements= .=20 =20 + Printing out problematic blocks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you want to print out a disassembly of a particular block that |