[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 229602] Parsing freeze UI when reading program's output directory
From:       Nicolas Bigaouette <nbigaouette () gmail ! com>
Date:       2011-02-01 22:39:33
Message-ID: 20110201223933.E34667C123 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=229602





--- Comment #16 from Nicolas Bigaouette <nbigaouette gmail com>  2011-02-01 23:39:30 ---
Created an attachment (id=56768)
 --> (http://bugs.kde.org/attachment.cgi?id=56768)
Callgrind file (1/2)

I've run kdevelop through valgrind using:
valgrind --tool=callgrind kdevelop
I've let it settle for many minutes, then launched the code's calculation which
generates a lot of output files. I've let valgrind run for an hour and a half.

I'm attaching the compressed file.
3d7395ef5a8f1c4fefe4ca37b04ea64e  callgrind.out.18545
74794673899f91e338e8333b82a3e573  callgrind.out.18545.7z

I'm not sure if kdevelop was compiled with debug symbols as it was installed
through Arch's package manager. If it needs a recompile, let me know.

Hopefully you'll see the behaviour in the file. If you need anything else, let
me know.

Thank you!

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]