Matthias, Matthias Klose wrote: > On 26.08.2009 16:38, Daigo Moriwaki wrote: >> Could you elaborate the reason of restricting only to ia64? > > it's not needed by default on architectures other than ia64. only the > unwinding in gcc on ia64 uses the library by default. it's unused on all > other archs.
Google-perftools describes[1]: > Perftools-Specific Install Notes > ================================ > > *** NOTE FOR 64-BIT LINUX SYSTEMS > > The glibc built-in stack-unwinder on 64-bit systems has some problems > with the perftools libraries. (In particular, the cpu/heap profiler > may be in the middle of malloc, holding some malloc-related locks when > they invoke the stack unwinder. The built-in stack unwinder may call > malloc recursively, which may require the thread to acquire a lock it > already holds: deadlock.) > > For that reason, if you use a 64-bit system, we strongly recommend you > install libunwind before trying to configure or install google > perftools. Libunwind on x86_64 is of use, at least, for google-perftools. What do you think? [1] http://code.google.com/p/google-perftools/source/browse/trunk/INSTALL -- Daigo Moriwaki daigo at debian dot org -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
