[valgrind] [Bug 457860] Memcheck classifies leaks differently depending on if a C program exits with `return` or `exit`
https://bugs.kde.org/show_bug.cgi?id=457860 Paul Floyd changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Paul Floyd --- I don't think that this is a bug and don't see much benefit in trying to change the behaviour. Both reports should be clear enough to find the memory. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457860] Memcheck classifies leaks differently depending on if a C program exits with `return` or `exit`
https://bugs.kde.org/show_bug.cgi?id=457860 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457860] Memcheck classifies leaks differently depending on if a C program exits with `return` or `exit`
https://bugs.kde.org/show_bug.cgi?id=457860 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --- This is because when you return the stack frame for main is discarded and "a" is no longer live but when you call exit that stack frame still exists and "a" is still live as a result. I think it would be quite hard for valgrind to figure out that exit had been called and then where to unwind the stack to which is what would be needed to get the two to behave the same. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457860] Memcheck classifies leaks differently depending on if a C program exits with `return` or `exit`
https://bugs.kde.org/show_bug.cgi?id=457860 Dylan Brotherston changed: What|Removed |Added CC||dylanbbbrot...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
