Hi,
I tried tcmalloc but the results are the same. RSS memory usage is
even slightly higher when I used tcmalloc
RSS after main initialization
glibcMalloc : 2080KB
tcMalloc: 2756KB
RSS after XML node initialization
glibcMalloc : 7004KB
tcMalloc: 7560KB
RSS after removing the XML node
glibc
On Tue, 2012-02-14 at 23:58 +, Rob wrote:
> > Hmm, this doesn't sound like it's going to be simple to fix in
> > a clean way.
> >
> > For the moment, can we do the incremental fix of taking Philippe's
> > patch (with the off-by-one fixed) ? That's a very simple patch
> > and uncontroversial pa
Hello. I downloaded the development version of valgrind from
Subversion today. It configured and built fine, but while trying to
run it on my application, I got this error during the run:
vex amd64->IR: unhandled instruction bytes: 0xC2 0x0 0x0 0x66 0x66
0x66 0x90 0x66
==10739== valgrind: Unreco
Jakub Kubinski wrote:
> Hi,
>
> I tried tcmalloc but the results are the same. RSS memory usage is
> even slightly higher when I used tcmalloc
This test is inconclusive since tcmalloc never returns freed memory to the OS.
Also, while tcmalloc has greater overhead in a single-threaded program, it
> Hello. I downloaded the development version of valgrind from
> Subversion today.
Thank you for mentioning the version of valgrind!
> It configured and built fine, but while trying to
> run it on my application, I got this error during the run:
>
> vex amd64->IR: unhandled
On 16/02/12 02:26, Patrick J. LoPresti wrote:
> Disassembly of myApp leading up to 0x1FF07B5:
>
> 0x1ff07aa<__intel_get_new_mem_ops_cpuid+26>:mov%edx,0xc(%r9)
> 0x1ff07ae<__intel_get_new_mem_ops_cpuid+30>:pop%rdx
> 0x1ff07af<__intel_get_new_mem_ops_cpuid+31>:
