search

CodeJuan / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Cant compile gproftools with mips64 #666

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I compile gpreftools and recive error:
ork/matnowak/gperf/out/lib -DHAVE_CONFIG_H -I. -I./src -I./src -Wall 
-Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -fno-builtin-malloc 
-fno-builtin-free -fno-builtin-realloc -fno-builtin-calloc -fno-builtin-cfree 
-fno-builtin-memalign -fno-builtin-posix_memalign -fno-builtin-valloc 
-fno-builtin-pvalloc -Wno-unused-result -g -O2 -MT src/stacktrace.lo -MD -MP 
-MF src/.deps/stacktrace.Tpo -c src/stacktrace.cc  -fPIC -DPIC -o 
src/.libs/stacktrace.o
src/stacktrace.cc:213:2: error: #error Cannot calculate stack trace: will need 
to write for your environment
src/stacktrace.cc: In function 'int GetStackFrames(void**, int*, int, int)':
src/stacktrace.cc:222:23: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'int GetStackFramesWithContext(void**, int*, 
int, int, const void*)':
src/stacktrace.cc:227:23: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'int GetStackTrace(void**, int, int)':
src/stacktrace.cc:234:23: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'int GetStackTraceWithContext(void**, int, int, 
const void*)':
src/stacktrace.cc:239:23: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'void init_default_stack_impl_inner()':
src/stacktrace.cc:251:7: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'void init_default_stack_impl()':
src/stacktrace.cc:261:77: error: 'get_stack_impl' was not declared in this scope
src/stacktrace.cc: In function 'int GetStackTraceWithContext(void**, int, int, 
const void*)':
src/stacktrace.cc:241:1: warning: control reaches end of non-void function 
[-Wreturn-type]
src/stacktrace.cc: In function 'int GetStackTrace(void**, int, int)':
src/stacktrace.cc:235:1: warning: control reaches end of non-void function 
[-Wreturn-type]
src/stacktrace.cc: In function 'int GetStackFramesWithContext(void**, int*, 
int, int, const void*)':
src/stacktrace.cc:230:1: warning: control reaches end of non-void function 
[-Wreturn-type]
src/stacktrace.cc: In function 'int GetStackFrames(void**, int*, int, int)':
src/stacktrace.cc:223:1: warning: control reaches end of non-void function 
[-Wreturn-type]
make: *** [src/stacktrace.lo] Error 1

What can i do ??

Original issue reported on code.google.com by mateusz....@gmail.com on 21 Jan 2015 at 12:32

GoogleCodeExporter commented 9 years ago 
option 1: get libunwind

option 2: build only malloc via ./configure --enable-minimal

Original comment by alkondratenko on 21 Jan 2015 at 3:24

GoogleCodeExporter commented 9 years ago 
hi that helps, but i have to find memory leaks in my app on mips64
architecture. I wanted to use valgrind but thorows segmentation fault.
Using -ltcmalloc_minimal when i run my application
env HEAPCHECK=normal ./a.out
i get no informaiton about leaks. When i use -ltcmalloc on x86 i get proper
output. Can memory leaks be debug with tcmalloc_minimal. ??

Wed Jan 21 2015 at 15:24:15 użytkownik <gperftools@googlecode.com> napisał:

Original comment by mateusz....@gmail.com on 22 Jan 2015 at 9:55

GoogleCodeExporter commented 9 years ago 
No. Heapchecker is part of full tcmalloc library.

Then you'll need to either get yourself working libunwind or other way to 
capture backtraces. --enable-stacktrace-via-backtrace might work for 
heapchecker.

See for example this thread: 
https://groups.google.com/forum/#!searchin/google-perftools/mips/google-perftool
s/19HpS8Xaeoo/tONQyTFAjCAJ

Original comment by alkondratenko on 22 Jan 2015 at 3:58

GoogleCodeExporter commented 9 years ago 
I ale wady have libunwind compiled for mips64 and i gór errors from First
mail while i do make install

czw., 22 sty 2015, 16:58 null użytkownik <gperftools@googlecode.com>
napisał:

Original comment by mateusz....@gmail.com on 22 Jan 2015 at 4:42

GoogleCodeExporter commented 9 years ago 
Then it means that configure script was unable to find libunwind.

Usually inspecting config.log will hint you why.

Original comment by alkondratenko on 22 Jan 2015 at 5:21