Comments (4)
What machine architecture are you running on: intel, powerpc, other? See the
top of
the INSTALL file for details about what tests do not yet pass on what systems.
If you could include the full output of the make check output, that may also be
helpful in figuring out what's going wrong.
Original comment by [email protected]
on 9 Feb 2008 at 12:15
from gperftools.
The x86_64 architecture which is mentioned in the subject is an Intel 64-bit
architecture.
For the full output of make check, see also the attachment make-check-output.txt
Original comment by [email protected]
on 9 Feb 2008 at 7:14
Attachments:
from gperftools.
Update: when running the command below, all 22 tests pass:
$ ./configure --enable-frame-pointer && make && make check
...
===================
All 22 tests passed
===================
Can the configure script please be modified such that on x86_64
--enable-frame-pointer is enabled automatically ?
Original comment by [email protected]
on 9 Feb 2008 at 7:24
from gperftools.
Doh! -- I missed the subject line when looking for the machine info. Sorry
about that.
} Update: when running the command below, all 22 tests pass:
} $ ./configure --enable-frame-pointer && make && make check
Ah, I'm glad that fixed it.
} Can the configure script please be modified such that on x86_64
} --enable-frame-pointer is enabled automatically ?
Alas, it's not that simple; if you use --enable-frame-pointer, you also need to
ensure the other libraries you link in, including libc and libc++, have frame
pointers enabled. This is not something the configure script can determine (as
far
as I know). It also requires that you compile all applications that link in
-ltcmalloc with -fno-omit-frame-pointers. Overall, this is a brittle setting
that
requires user awareness to work properly; it's not something best done
automatically.
That said, --enable-frame-pointer should not be necessary if you're using
libunwind,
which it sounds like you were doing. Perhaps you were running into some of the
problems mentioned in the '64 bit notes' in the README. It's hard to tell from
the
logs you included unfortunately: I can see that the relevant tests are
segfaulting,
but can't tell much about why.
If I have a chance I'll see I can reproduce this locally on my own x86_64
development
machine. Even if so, I'm not sure how much we can do to improve the situation.
The
fact x86_64 omits the frame pointer by default makes life difficult for us!
But I
know libunwind is being actively developed in its own right, and improvements
there
should benefit these tests as well.
Original comment by [email protected]
on 9 Feb 2008 at 7:58
- Changed state: WontFix
from gperftools.
Related Issues (20)
- VIRT memory continues to grow when using 64k byte buffers HOT 4
- Linking libtorsocks with libtcmalloc results in SIGSEGV HOT 5
- What will be the official home for gperftools? HOT 2
- On Windows 8.1, system-alloc_unittest fails an assert HOT 1
- recalloc is wrong in windows/override_functions.cc HOT 1
- src/malloc_hook_mmap_linux.h fails to compile with clang in C++11 mode when targeting 32 bit with _FILE_OFFSET_BITS=64 HOT 1
- Should heap profiling with mingw work? HOT 4
- src/gperftools/tcmalloc.h and src/windows/gperftools/tcmalloc.h report v2.3 HOT 2
- msvc14 (visual studio 15) timespec type redefinition HOT 1
- [PATCH] Improve CPUPROFILE_PER_THREAD_TIMERS HOT 13
- Tcmalloc crashes when process adds an mmap block close to the top of the heap HOT 8
- failed to compile gperftools with "-march=armv8-a+crc" HOT 3
- Failed to build with lib musl HOT 1
- MongoDB version 3.0 build from source fails due to gperftools 2.2 on PPC64 HOT 2
- MallocExtension::GetStats() is not implemented HOT 1
- futex handling is weird (and wrong on arm) HOT 2
- Warning about non-virtual destructor in class with virtual methods HOT 1
- allow avoiding the hardcoded /tmp/google.alloc path for tracing output HOT 1
- It doesn't work on s390x architecture
- Why tcmalloc fail when I compile run program with shared library?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gperftools.