[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2023-08-02 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=463514 Bug Janitor Service changed: What|Removed |Added Resolution|NOT A BUG |WORKSFORME Status|NEEDSINFO

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2023-07-18 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #11 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2023-07-03 Thread m
https://bugs.kde.org/show_bug.cgi?id=463514 m changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |N

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2023-07-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #9 from Paul Floyd --- (In reply to m from comment #8) > Is this still an issue? Memcheck not detecting leaks for allocations that the compiler optimizes away was never an issue. Unreproducible errors that don't get more information after

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2023-07-03 Thread m
https://bugs.kde.org/show_bug.cgi?id=463514 m changed: What|Removed |Added CC||kde.si...@dralias.com --- Comment #8 from m --- Is this st

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-29 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #7 from Paul Floyd --- disInstr(arm): unhandled instruction: 0xEC510F1E cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE) ==28938== valgrind: Unrecognised instruction at address 0x48d0bc8. ==28938==at 0x48D0BC8: ??? (in /sy

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-28 Thread Raju Ponnagani
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #6 from Raju Ponnagani --- Hello Paul Floyd, I tried the same leak application with Valgrind 3.20 version in android(arm32 bit architecture) and this time the leaked summary is not generated. please check the below report. Valgrind command

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #5 from Paul Floyd --- (In reply to Raju Ponnagani from comment #4) > Verified with the changes as you mention, leaks get detected under > definitely lost of Leak Summary. But not shows the exact function name > (leak_func ) where the leak h

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-28 Thread Raju Ponnagani
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #4 from Raju Ponnagani --- Verified with the changes as you mention, leaks get detected under definitely lost of Leak Summary. But not shows the exact function name (leak_func ) where the leak happened in the application. Code Snippet:- int

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=463514 --- Comment #3 from Paul Floyd --- OK, next thing, make sure that your heap memory really is being allocated. You have ptr = (char *) calloc(1,20); ptr = "Hello World\n"; I'm not sure if it is intentional to overwrite the 'ptr' pointer

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-27 Thread Raju Ponnagani
https://bugs.kde.org/show_bug.cgi?id=463514 Raju Ponnagani changed: What|Removed |Added CC||shivaraju173ponnagani@gmail

[valgrind] [Bug 463514] Valgrind not detecting the leaks.

2022-12-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=463514 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd