google-perftools Google Group

Re: Issue 190 in google-perftools: Feature request: expose API to record stacktrace

2009-11-18T22:29:23Z

We have C++ code that records the current stacktrace with an arbitrary
passed-in value, and is able to emit the results in a format readable by
'pprof'. We use this for instrumenting our own mutexes, for example, to do
contention profiling.

I can send a patch soon.

Re: Issue 192 in google-perftools: CFLAGS not passed consistently

2009-11-18T19:36:26Z

Updates:
Labels: Type-Defect Priority-Medium

Comment #1 on issue 192 by csilvers: CFLAGS not passed consistently
[link]

What does that mean? Perhaps you can explain what "passing CFLAGS
consistently"
consists of.

Also, perftools is C++, so almost everything is carried in CXXFLAGS.

Issue 192 in google-perftools: CFLAGS not passed consistently

2009-11-18T17:52:52Z

Status: New
Owner: ----

New issue 192 by i.ga...@brainsware.org: CFLAGS not passed consistently
[link]

I am trying to compile tcmalloc on Debian 64 with hardening-gcc installed
and enabled.

This looks as follows:

i.galic@panic ~ % gcc --version

Re: Issue 154 in google-perftools: env HEAPCHECK=normal ./myapp just doesn't work on Linux

2009-11-17T19:14:41Z

Updates:
Status: NotABug

Comment #9 on issue 154 by csilvers: env HEAPCHECK=normal ./myapp just
doesn't work on Linux
[link]

OK, I'm going to close this as NotABug, then, since it doesn't seem to be a
problem
in perftools. I'm not sure if there's a good way to modify the test to

Re: Issue 154 in google-perftools: env HEAPCHECK=normal ./myapp just doesn't work on Linux

2009-11-17T19:04:32Z

Comment #8 on issue 154 by a.cheusov: env HEAPCHECK=normal ./myapp just
doesn't work on Linux
[link]

With "ulimit -s unlimited" "make check" succeeds for 1.3 and 1.4.

--
You received this message because you are listed in the owner

Re: Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-17T18:29:54Z

Comment #5 on issue 191 by csilvers: 1.4 debug crashes on double free
[link]

What kind of change are you looking for? Do you want to make it so that
the code
doesn't crash on double-free? Or do you just really need it to be printing

Re: Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-17T16:52:00Z

Comment #4 on issue 191 by JassenM: 1.4 debug crashes on double free
[link]

Can you please point me to the location of the tcmalloc code and the change
that
needs to be made so I can patch this myself?

--
You received this message because you are listed in the owner

Re: Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-17T16:47:57Z

Comment #3 on issue 191 by csilvers: 1.4 debug crashes on double free
[link]

Yes, free() and delete are the same internally. In both cases, a
double-free will
crash, rather than print an error message and *then* crash. So the
functionality

Re: Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-17T16:38:41Z

Comment #2 on issue 191 by JassenM: 1.4 debug crashes on double free
[link]

Does this impact the free() function of tcmalloc_debug, that is double
free()?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.

Re: Issue 179 in google-perftools: Build fail in Snow Leopard

2009-11-16T21:59:26Z

Comment #6 on issue 179 by csilvers: Build fail in Snow Leopard
[link]

OK, I got a snow leopard machine, but it's 32-bit. I think your system is
64-bit?
(That's where we try to use libunwind.) Everything works properly for me.

I'll try to get a 64-bit snow leopard machine, but that may be harder for

Re: Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-16T19:25:38Z

Updates:
Status: Started
Labels: Type-Defect Priority-Medium

Comment #1 on issue 191 by csilvers: 1.4 debug crashes on double free
[link]

You're absolutely right! Our code to print a double-free warning got some
bitrot at
some point, and stopped working. We'll fix that up for the next release.

Issue 191 in google-perftools: 1.4 debug crashes on double free

2009-11-16T17:08:46Z

Status: New
Owner: ----

New issue 191 by nkiesel: 1.4 debug crashes on double free
[link]

What steps will reproduce the problem?
1. Compile the following program and link against any tcmalloc_debug variant
int main(int, char **)
{
int * pint = new int;

Re: Issue 190 in google-perftools: Feature request: expose API to record stacktrace

2009-11-16T16:52:23Z

Comment #5 on issue 190 by mohit.aron: Feature request: expose API to
record stacktrace
[link]

Ok - I can work on that. But I may not be able to get to it soon.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.

Re: Issue 190 in google-perftools: Feature request: expose API to record stacktrace

2009-11-16T16:36:11Z

Comment #4 on issue 190 by csilvers: Feature request: expose API to record
stacktrace
[link]

Ok, I think the best plan of attack is for you to propose a patch, and we
can go from
there. Ideally, the patch would include an actual user of this code so we

Re: Comparison vs. STLPort allocator

2009-11-16T16:24:47Z

There are some comparisons against ptmalloc2 (the default glibc
malloc) in
[link]

I don't know of any other comparisons, though.

craig