https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #8 from shapath ---
Thanks, Philippes for the response.
So does this means that Valgrind will report false positives for LDL if
structure packing is used?
As I mentioned this is a third-party code and structure packing is used for
many
https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #6 from shapath ---
I understand the reachable part but not able to understand
==30830== 6 bytes in 1 blocks are definitely lost in loss record 1 of 2
==30830==at 0x4C29F73: malloc (vg_replace_malloc.c:309)
==30830==by 0x4EC3B89
https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #5 from shapath ---
(In reply to Philippe Waroquiers from comment #4)
> (In reply to shapath from comment #3)
> >
> > Valgrind report:-
> > ==
> > (gdb) monitor leak_check full reachable any
> When
https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #3 from shapath ---
Thank you guys for the response !!!
The leak is reported in third-party code. Based on your responses and input I
analyzed the code and wrote a similar sample program where i was able to hit
this.
The interesting thing
https://bugs.kde.org/show_bug.cgi?id=455826
shapath changed:
What|Removed |Added
CC||m...@gmail.com
--
You are receiving this mail
r 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.
