https://bugs.kde.org/show_bug.cgi?id=455826
Bug ID: 455826
Summary: Running Valgrind memcheck on a live process without
exiting it reports LDL but on graceful exit it does
not.
Product: valgrind
Version: 3.17.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: meeee...@gmail.com
Target Milestone: ---
SUMMARY
Hello Guys,
Not sure this is a bug but i would like to understand the behavior. I have gone
through Valgrind references as well.
I am trying to monitor leaks using vgdb on a running process. using the below
reference.
Reference:- https://valgrind.org/docs/manual/manual-core-adv.html
Step 1. Run valgrind with vgdb.
valgrind --tool=memcheck --leak-check=full --show-reachable=yes --vgdb=yes
--undef-value-errors=yes --track-origins=yes --child-silent-after-fork=no
--trace-children=no --error-exitcode=1 --log-file=/var/log/_valgrind_%p
--xml-file=/var/log/_valgrind_xml_%p <application>
Step2.
Run gdb and attach to the process using:-
"target remote | vgdb"
Step3.
Run "monitor leak_check full reachable any".
After running this I see LDL (leak definitely lost.) in the report. But if I
gracefully exit the program i do not see these leaks in the generated report.
Is it possible that "monitor " is getting called at a random state of the
application and treats the pointers as LDL that are going to be freed at the
shutdown as lost memory ?
Is there a possibility that the monitor tool is reporting them as false
positives?
Or these are definite leaks that are somehow handled by some pointer arithmetic
or something else.
Please point me to any reference if it is already available.
Thanks
Shapath
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(
--
You are receiving this mail because:
You are watching all bug changes.
