provide info for addresses accessed in errors reported

From derek.br...@gmail.com on December 10, 2010 17:57:53

PR 423750

suggestion: providing symbol info not only for instructions but also for the data accessed. not just for data section addresses, but also stack locations: we should be able to look up local variables in some cases since we have the containing function.

extending beyond symbol info:

• for heap, size of malloc block, callstack for where allocated (only if -check_leaks?), and by which thread and at what time (=> PR 465163)
• for delayed free, callstack of the free point

we have had requests for including the address target itself in results.txt so we should start w/ that and basic symbol info

with client checking dups now (PR 484167) we'll need to print out a special line for each dup w/ the per-instance info

should also include the "within 0x-0x" info from PR 532205

should also include the malloc info from PR 535568

I already did:

• added propagation of heap info from this tree to results.txt as separate "Note:" lines. this case covers providing this info on dups not just 1st unique, and further ideas of including callstacks of the nearest and freed heap chunks

Original issue: http://code.google.com/p/drmemory/issues/detail?id=129