[Valgrind-developers] valgrind: r4995 - trunk

[<sv...@va...>]

Author: njn
Date: 2005-11-03 16:24:53 +0000 (Thu, 03 Nov 2005)
New Revision: 4995

Log:
Record a useful nugget from Julian.

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	2005-11-03 13:46:30 UTC (rev 4994)
+++ trunk/README_DEVELOPERS	2005-11-03 16:24:53 UTC (rev 4995)
@@ -77,3 +77,16 @@
 At the time of writing the allocator is not annotated with client reques=
ts
 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.
+
+Printing out problematic blocks
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+If you want to print out a disassembly of a particular block that
+causes a crash, do the following.
+
+Try running with "--vex-guest-chase-thresh=3D0 --trace-flags=3D10000000
+--trace-notbelow=3D999999".  This should print one line for each block
+translated, and that includes the address.
+
+Then re-run with 999999 changed to the highest bb number shown.
+This will print the one line per block, and also will print a
+disassembly of the block in which the fault occurred.