On Thu, 2013-04-18 at 08:50 -0700, Brian Budge wrote:
Hi Paul. I am at 20% of memory use. I should also note that I
followed Julian's advice for increasing vg_n_segments and memory size
to 128 GB.
Does valgrind itself do anything multithreaded? My program uses all
cores on the machine at
On Tue, Apr 23, 2013 at 1:04 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
Some prototyping was done of a non serialised valgrind.
See https://bugs.kde.org/show_bug.cgi?id=301830
and the MTV branch in svn.
This prototype is not usable in its current state: only the
none tool
On Tue, 2013-04-23 at 13:08 -0700, Brian Budge wrote:
Some prototyping was done of a non serialised valgrind.
See https://bugs.kde.org/show_bug.cgi?id=301830
and the MTV branch in svn.
This prototype is not usable in its current state: only the
none
- Original Message -
Hi all -
I've been using valgrind for a long time. I just upgraded to 3.81,
and I see my %CPU in top at close to 1000. I think I've only ever
seen 100 or less before. One difference is that this time I used
--enable-tls. Does this actually allow threads to work
Hi all -
I've been using valgrind for a long time. I just upgraded to 3.81, and I
see my %CPU in top at close to 1000. I think I've only ever seen 100 or
less before. One difference is that this time I used --enable-tls. Does
this actually allow threads to work concurrently?
Thanks,
Brian
