20 Jul 22:00 2016mathog
*Trouble using more than 24Gb memory on 64 bit system with 512G
20 Jul 23:45 2016mathog
**Trouble using more than 24Gb memory on 64 bit system with 512G
21 Jul 16:09 2016Julian Seward
**Trouble using more than 24Gb memory on 64 bit system with 512G
21 Jul 16:17 2016Julian Seward
***Trouble using more than 24Gb memory on 64 bit system with 512G
21 Jul 18:28 2016mathog
****Trouble using more than 24Gb memory on 64 bit system with 512G
20 Jul 20:13 2016simon.goda
*Difference in Behaviour between 3.10 and 3.11
21 Jul 16:22 2016Julian Seward
**Difference in Behaviour between 3.10 and 3.11
22 Jul 10:29 2016simon.goda
**Difference in Behaviour between 3.10 and 3.11
22 Jul 12:27 2016Julian Seward
***Difference in Behaviour between 3.10 and 3.11
15 Jul 19:38 2016James Orr
*New User. Probably a Simple User Error...
15 Jul 21:25 2016Trey Boudreau
**New User. Probably a Simple User Error...
15 Jul 21:32 2016James Orr
***New User. Probably a Simple User Error...
16 Jul 00:40 2016John Reiser
****New User. Probably a Simple User Error...
11 Jul 03:18 2016Eqbal
*running callgrind with JNI (libhdfs) does not work
8 Jul 01:03 2016Stepan Zakharov
*Callgrind longest possible run
8 Jul 12:50 2016Konstantin Tokarev
**Callgrind longest possible run
8 Jul 13:38 2016Stepan Zakharov
**Callgrind longest possible run
8 Jul 22:09 2016Philippe Waroquiers
***Callgrind longest possible run
12 Jul 14:23 2016Josef Weidendorfer
**Callgrind longest possible run
12 Jul 15:23 2016Milian Wolff
***Callgrind longest possible run
7 Jul 14:59 2016E. G. Patrick Bos
*trace function calls from individual objects in callgrind
7 Jul 16:45 2016Jim Cromie
**trace function calls from individual objects in callgrind
5 Jul 03:22 2016Yang Liu
*How can callgrind_annotate output call times instead of instruction co
5 Jul 10:37 2016Josef Weidendorfer
**How can callgrind_annotate output call times instead of instruction co
27 Jun 18:08 2016Ana Rey
*Merge multiple callgrind output files into one
28 Jun 10:16 2016Milian Wolff
**Merge multiple callgrind output files into one
29 Jun 19:42 2016Josef Weidendorfer
**Merge multiple callgrind output files into one
23 Jun 20:36 2016Rick Leir
*llvm clang
23 Jun 21:20 2016Philippe Waroquiers
**llvm clang
21 Jun 17:44 2016Tobias Widlund
*[SPAM] precious memories
20 Jun 10:56 2016Schmidt, Adriaan
*Memory mapping and READ_IMPLIES_EXEC
20 Jun 13:19 2016Tom Hughes
**Memory mapping and READ_IMPLIES_EXEC
21 Jun 09:07 2016Schmidt, Adriaan
***Memory mapping and READ_IMPLIES_EXEC
18 Jun 17:52 2016Jeffrey Walton
*Failed to start tool 'memcheck' for platform 'amd64-solaris': No such
18 Jun 17:30 2016Jeffrey Walton
*Failed to start tool 'memcheck' for platform 'amd64-solaris': No such
18 Jun 11:19 2016Jeffrey Walton
*Failed to start tool 'memcheck' for platform 'amd64-solaris': No such
18 Jun 15:54 2016Ivo Raisr
**Failed to start tool 'memcheck' for platform 'amd64-solaris': No such
17 Jun 15:42 2016Alex Bligh
*Thread confusion on OS-X
17 Jun 18:50 2016Alex Bligh
**Thread confusion on OS-X
17 Jun 19:37 2016John Reiser
***Thread confusion on OS-X
17 Jun 20:30 2016Alex Bligh
****Thread confusion on OS-X
17 Jun 20:29 2016Alex Bligh
**Thread confusion on OS-X
9 Jun 17:13 2016Yang Liu
*How does callgrind detect loops?
17 Jun 15:03 2016Josef Weidendorfer
**How does callgrind detect loops?
9 Jun 15:24 2016Kirill Frolov
*How can I annotate source code to stop valgrind's DRD tool complain ab
10 Jun 06:49 2016Ivo Raisr
**How can I annotate source code to stop valgrind's DRD tool complain ab
10 Jun 15:32 2016Kirill Frolov
***How can I annotate source code to stop valgrind's DRD tool complain ab
2 Jun 04:09 2016fd067162
*[SPAM] ✉ just a note
26 May 06:18 2016Marshall Lochbaum
*Usage and output with memory pools
26 May 12:06 2016John Reiser
**Usage and output with memory pools
26 May 19:13 2016Marshall Lochbaum
***Usage and output with memory pools
27 May 06:27 2016John Reiser
****Usage and output with memory pools
1 Jun 18:16 2016Marshall Lochbaum
*****Usage and output with memory pools
1 Jun 19:19 2016John Reiser
******Usage and output with memory pools
1 Jun 22:07 2016Philippe Waroquiers
*******Usage and output with memory pools
24 May 06:50 2016Jonathan Bennett
*Signal handlers not being called under valgrind
24 May 20:01 2016Jonathan Bennett
**Signal handlers not being called under valgrind
19 May 03:26 2016Ricardo Telichevesky
*CPUID
19 May 06:50 2016jreiser
**CPUID
14 May 04:37 2016Brian Weston
*Valgrind Installation Error
10 May 02:20 2016Benoit Escarmelle
*[SPAM] Fw: new message
6 May 15:26 2016m.bibby
*[SPAM] Fw: new message
4 May 10:02 2016Philippe Waroquiers
*[SPAM] Fw: new message
4 May 10:00 2016Benoit Escarmelle
**[SPAM] Fw: new message
25 Apr 21:50 2016Deene Dafoe
*Invalid read/write in memory mapped segments
25 Apr 18:11 2016Николай Жосов
*Fwd: ASan error using memcheck tool
25 Apr 18:33 2016Tom Hughes
**Fwd: ASan error using memcheck tool
25 Apr 18:50 2016Nick
**Fwd: ASan error using memcheck tool
25 Apr 22:09 2016John Carter
***Fwd: ASan error using memcheck tool
18 Apr 23:56 2016folkert
*suppressing warnings about std::atomic_bool
15 Apr 02:56 2016John Reiser
*expected results for regtest
15 Apr 09:38 2016Ivo Raisr
**expected results for regtest
15 Apr 18:43 2016Mark Roberts
***expected results for regtest
15 Apr 22:33 2016Mark Wielaard
***expected results for regtest
16 Apr 00:36 2016John Reiser
****expected results for regtest
16 Apr 06:29 2016Ivo Raisr
****expected results for regtest
14 Apr 00:52 2016Mark Roberts
*expected results for regtest
14 Apr 02:17 2016John Reiser
**expected results for regtest
13 Apr 13:01 2016Jürgen Kadidlo
*Helgrind never shows how the lock order was established
12 Apr 12:52 2016venkat konamki
*Not able to get the Leak summery details in ARM architecture
12 Apr 13:16 2016Tom Hughes
**Not able to get the Leak summery details in ARM architecture
12 Apr 14:48 2016venkat konamki
***Not able to get the Leak summery details in ARM architecture
6 Apr 14:09 2016PRASHANT PATEL
*Is is possible to use "valgrind --tool=callgrind" command in "excelp"
6 Apr 14:30 2016Tom Hughes
**Is is possible to use "valgrind --tool=callgrind" command in "excelp"
6 Apr 15:20 2016PRASHANT PATEL
***Is is possible to use "valgrind --tool=callgrind" command in "excelp"
31 Mar 10:38 2016Harish Babu
*Help running valgrind
31 Mar 11:00 2016Tom Hughes
**Help running valgrind
30 Mar 10:59 2016David Faure
*helgrind: false race positive with static variable in function
30 Mar 11:28 2016Ivo Raisr
**helgrind: false race positive with static variable in function
4 Apr 08:49 2016David Faure
***helgrind: false race positive with static variable in function
26 Mar 20:15 2016Burlen Loring
*0 bytes inside a block of size 30,121
27 Mar 12:08 2016Tom Hughes
**0 bytes inside a block of size 30,121
28 Mar 04:29 2016Burlen Loring
***0 bytes inside a block of size 30,121
25 Mar 23:33 2016David Niklas
*Multi threading
24 Mar 21:50 2016Troy Heitmann
*Insight as to why Valgrind shows memory leak for LAPACKE_dgbsv
25 Mar 17:45 2016paulf
**Insight as to why Valgrind shows memory leak for LAPACKE_dgbsv
19 Mar 22:02 2016David Faure
*helgrind, clang and thread_local
21 Mar 14:56 2016Alexander Potapenko
**helgrind, clang and thread_local
22 Mar 09:28 2016David Faure
***helgrind, clang and thread_local
17 Mar 10:25 2016Dor Ben Dov
*Multi-threading