[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 --- Comment #6 from Robin Kuzmin --- Makes sense for me. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 --- Comment #5 from Philippe Waroquiers --- (In reply to Robin Kuzmin from comment #4) > I have run through this discussion more thoroughly. My understanding how > valgrind works (or should work) has changed. Here is my

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 --- Comment #4 from Robin Kuzmin --- I have run through this discussion more thoroughly. My understanding how valgrind works (or should work) has changed. Here is my vision. In order to avoid multiple reports of the same error,

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 --- Comment #3 from Robin Kuzmin --- You wrote: If suppressions would have to be done without taking --num-callers into account, then it means that all errors stacktraces would have to be first recorded without limit, and then

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 Philippe Waroquiers changed: What|Removed |Added CC|

[valgrind] [Bug 199468] Suppressions: stack size limited to 25 while --num-callers allows up to 50 frames

https://bugs.kde.org/show_bug.cgi?id=199468 Robin Kuzmin changed: What|Removed |Added CC||kuzmin.ro...@gmail.com