https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #26 from Eric Chamberland ---
(In reply to Eric Chamberland from comment #25)
> FWIW, the svn version of valgrind didn't produced any blockSane assertion
> last night, but since it was randomly happening, we have to let go som
https://bugs.kde.org/show_bug.cgi?id=475484
Bug ID: 475484
Summary: How to have "source" tab
Classification: Developer tools
Product: kcachegrind
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=475484
--- Comment #1 from Eric Chamberland ---
Created attachment 162231
--> https://bugs.kde.org/attachment.cgi?id=162231&action=edit
Tabs from freshly compiled version
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475484
--- Comment #2 from Eric Chamberland ---
Created attachment 162232
--> https://bugs.kde.org/attachment.cgi?id=162232&action=edit
Tabs with "source" (at top of window) in qcachegrind and source view
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=475484
--- Comment #3 from Eric Chamberland ---
Here is the corrected step #3 to reproduce:
> STEPS TO REPRODUCE
...
> 3. echo -e '#include \nint main() {std::cout << "Hello World" <<
> std::endl;return 0;}'
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #26 from Eric Chamberland ---
(In reply to Eric Chamberland from comment #25)
> FWIW, the svn version of valgrind didn't produced any blockSane assertion
> last night, but since it was randomly happening, we have to let go som
https://bugs.kde.org/show_bug.cgi?id=356457
Eric Chamberland changed:
What|Removed |Added
CC||eric.chamberl...@gmail.com
--- Comment #16
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #17 from Eric Chamberland ---
(copied from valgrind-users list following Julian Seward request)
Hi,
I recently upgraded to valgrind 3.11.0 (was 3.8.1 before).
I also upgraded Intel MKL to the 2015 version.
We use valgrind since 2011-10
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #18 from Eric Chamberland ---
Some other informations:
Distribution: openSUSE 12.3
Kernel: cat /proc/version
Linux version 3.7.10-1.45-desktop (geeko@buildhost) (gcc version 4.7.2 20130108
[gcc-4_7-branch revision 195012] (SUSE Linux
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #21 from Eric Chamberland ---
Finally I got not 6 but 8 failing tests (wrote the report before they all
completed...)
I have 7 different libraries where valgrind hangs:
#1:
--17999-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #23 from Eric Chamberland ---
Thanks Joost for these informations: In fact, we will upgrade the os when
possible...
This morning, I have 4 (different) failing tests.
I launched 3.11.0 with -v -v -v -d -d -d, please see
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #24 from Eric Chamberland ---
Created attachment 101660
--> https://bugs.kde.org/attachment.cgi?id=101660&action=edit
valgrind launched with -v -v -v -d -d -d
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #25 from Eric Chamberland ---
FWIW, the svn version of valgrind didn't produced any blockSane assertion last
night, but since it was randomly happening, we have to let go some days to see
if this bug is definitely not occurring
https://bugs.kde.org/show_bug.cgi?id=356457
Eric Chamberland changed:
What|Removed |Added
CC||eric.chamberl...@gmail.com
--- Comment #16
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #17 from Eric Chamberland ---
(copied from valgrind-users list following Julian Seward request)
Hi,
I recently upgraded to valgrind 3.11.0 (was 3.8.1 before).
I also upgraded Intel MKL to the 2015 version.
We use valgrind since 2011-10
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #18 from Eric Chamberland ---
Some other informations:
Distribution: openSUSE 12.3
Kernel: cat /proc/version
Linux version 3.7.10-1.45-desktop (geeko@buildhost) (gcc version 4.7.2 20130108
[gcc-4_7-branch revision 195012] (SUSE Linux
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #21 from Eric Chamberland ---
Finally I got not 6 but 8 failing tests (wrote the report before they all
completed...)
I have 7 different libraries where valgrind hangs:
#1:
--17999-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #23 from Eric Chamberland ---
Thanks Joost for these informations: In fact, we will upgrade the os when
possible...
This morning, I have 4 (different) failing tests.
I launched 3.11.0 with -v -v -v -d -d -d, please see
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #24 from Eric Chamberland ---
Created attachment 101660
--> https://bugs.kde.org/attachment.cgi?id=101660&action=edit
valgrind launched with -v -v -v -d -d -d
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #25 from Eric Chamberland ---
FWIW, the svn version of valgrind didn't produced any blockSane assertion last
night, but since it was randomly happening, we have to let go some days to see
if this bug is definitely not occurring
20 matches
Mail list logo
