On Thu, May 12, 2011 at 08:55:32AM -0700, John Reiser wrote:
> >>> FWIW this is a matter of 227Mb large /usr/lib/valgrind versus 71Mb without
> >>> debug.
> >>
> >> Which machine architecture and compiler?
> >
> > amd64 gcc, but indeed with -g, because it's how binaries are supposed to
> > be buil
>>> FWIW this is a matter of 227Mb large /usr/lib/valgrind versus 71Mb without
>>> debug.
>>
>> Which machine architecture and compiler?
>
> amd64 gcc, but indeed with -g, because it's how binaries are supposed to
> be built in Debian.
For many [most?] packages, Fedora handles this by building _w
> write(1018, "C", 1) = 1
> rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
> read(162, "", 2952) = 0
> rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) =
> 0 gettid()= 30593
hi,
i just found out, that my (life) running server process, running unter
valgrind (because it's beta) is eating up 100% cpu, however, clients
connecting to it are served just fine, in terms of speed / responsivity.
As I should not just kill the process by now, I did an strace on it, to find
On Thu, May 12, 2011 at 07:58:14AM -0700, John Reiser wrote:
> > Hi, in the packaging readme[0] for valgrind it's stated that it's a bad
> > idea to strip what's in /usr/lib/valgrind/ ...
>
> > FWIW this is a matter of 227Mb large /usr/lib/valgrind versus 71Mb without
> > debug.
>
> Which machine
> Hi, in the packaging readme[0] for valgrind it's stated that it's a bad
> idea to strip what's in /usr/lib/valgrind/ ...
> FWIW this is a matter of 227Mb large /usr/lib/valgrind versus 71Mb without
> debug.
Which machine architecture and compiler?
There's a difference between stripped (applyin
Hello.
I was wondering if it is possible to run valgrind with
--leak-check=yes or =full without having valgrind check for use of
uninitialized values, memory invasion, memory corruption, etc. It would
be very useful since it must be many times faster than doing all these
checks.
Sorry
Hi, in the packaging readme[0] for valgrind it's stated that it's a bad
idea to strip what's in /usr/lib/valgrind/ because it makes bad reports.
Though if I test, here is what I get:
unstripped:
┌─(13:43)
└[apollon] valgrind ./a
==20112== Memcheck, a memory error detector
==20
