Hello,
I am using callgrind tool of valgrind to profile my running code.
Then I am using kcachegrind to view the output. The problem is that my
native code is already slow as it is. So running it through valgrind is
making it even more slow. According to my calculations, to run the code
just once
Hi,
Am 26.03.2013 13:54, schrieb Farah Saab Gmail:
I am using callgrind tool of valgrind to profile my running code.
Then I am using kcachegrind to view the output. The problem is that my
native code is already slow as it is. So running it through valgrind is
making it even more slow.
Feature-request:
Add backtrace to output for these warnings:
Warning: set address range perms: large range
[0x4c339040, 0x206094130) (undefined)
Explanation:
This was a large allocation which ate up all my memory when debugging
with valgrind making it hard for me to find where it
On Tue, 2013-03-26 at 14:30 +0100, Jonatan Wallmander wrote:
Feature-request:
Add backtrace to output for these warnings:
Warning: set address range perms: large range
[0x4c339040, 0x206094130) (undefined)
Probably not difficult to implement, however, see below ...