https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #4 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to shapath from comment #3) > > Valgrind report:- > ============== > (gdb) monitor leak_check full reachable any When compiling with gcc -g -O0 and doing the leak search, I do not get any definitely or possibly leaked block. Leak search reports 2 still reachable blocks. You can use the following to see why a block is still reachable: (where 0x4a330a0 is the addess of the strdup-ed "hello" (gdb) mo w 0x4a330a0 ==8392== Searching for pointers to 0x4a330a0 ==8392== tid 1 register R8 pointing at 0x4a330a0 (gdb) As you can see, in my case, the address of the just allocated name still happens to be in a register. When I force main to return, then name is reported as definitely leaked (as the register pointing to name is likely used for something else) -- You are receiving this mail because: You are watching all bug changes.
