[openbeos] Help with built-in profiling
- From: Stephan Assmus <superstippi@xxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 27 Nov 2006 23:29:32 +1300
Hello,
can someone here help me a bit to get on track with profiling? I have
successfully built the app_server in the test environment using the -pg GCC
switch. You have to provide an "mcount" function or link everything against
"/boot/develop/lib/x86/i386-mcount.o". The resulting executable runs very
slowly, so suppose something is happening. I tried using the "profile"
command, which supposedly spits out profiling information at the exit of
the programm that you run with it. But it just prints all the libraries
that the app_server links with when you invoke it and no further output
when I quit it. Has someone more insights? Can the "original" i386-mcount.o
even be used with the newer GCC?
Best regards,
-Stephan
- Follow-Ups:
- [openbeos] Re: Help with built-in profiling
- From: Jérôme Duval
- [openbeos] Re: Help with built-in profiling
- From: Axel Dörfler
Other related posts:
- » [openbeos] Help with built-in profiling
- » [openbeos] Re: Help with built-in profiling
- » [openbeos] Re: Help with built-in profiling
- [openbeos] Re: Help with built-in profiling
- From: Jérôme Duval
- [openbeos] Re: Help with built-in profiling
- From: Axel Dörfler