track undefined moves to identify origins of uninit errors

[derekbruening]

From [email protected] on December 10, 2010 17:58:13

PR 503222

xref the new Memcheck --track_origins feature

this would involve tracking uninit moves so that if an uninit error is raised the earliest operation touching the uninit data can be identified

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

[derekbruening]

From [email protected] on May 30, 2011 00:05:32

Also valueable: print the last system call which could init this memory range
(for example, the last syscall that was given a pointer to the same allocation)

[derekbruening]

From [email protected] on May 30, 2011 07:10:36

that's more for developers and not for users: users shouldn't have to analyze missing syscalls. eventually all the syscall info will be there. also, for unknown syscalls, when it's as simple as a primary parameter, the existing unknown syscall handling will already avoid uninits.

[derekbruening]

From [email protected] on July 12, 2012 19:32:29

split track origin of unaddressable error to issue #938

[derekbruening]

From [email protected] on May 14, 2014 12:25:00

As we have discussed offline in the past, for 32-bit we do not have a concrete path forward for this feature as we are unlikely to always fit multiple shadows and we do not want to serialize all threads. We will likely only implement it for 64-bit.