https://bugs.kde.org/show_bug.cgi?id=381304
Bug ID: 381304
Summary: RFE: --track-origins=yes identifies system call source
of Uninitialized value
Product: valgrind
Version: 3.13 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: jrei...@bitwagon.com
Target Milestone: ---
Request for enhancement (RFE): memcheck --track-origins=yes should report the
system call name (or number) if the "Uninitialised value was created" by a
system call. Currently the message gives the program counter value. In
general for most compiler-written code this is sufficient to identify the
source code.
However, for system calls there is an implementation style which sets up the
arguments separately for each call, then merges all syscalls into one tail.
This style makes it easy to track all system calls because there is only one
location which makes system calls. Unfortunately the program counter printed
by memcheck no longer identifies which syscall:
==25006== Conditional jump or move depends on uninitialised value(s)
==25006== at 0xF17E32: ???
==25006== Uninitialised value was created
==25006== at 0xF169C6: ???
==25006==
and 0xF169C6 is the address of the instruction after the one-and-only syscall
instruction, and is the same for any system call.
--
You are receiving this mail because:
You are watching all bug changes.
