Difference between revisions of "Valgrind"
From Apache OpenOffice Wiki
(→disabling the custom allocator) |
(pointer to Callgrind How-To) |
||
| Line 24: | Line 24: | ||
If you use a Vanilla build you want to grab the custom libsal_uno.so with that compiled in and LD_PRELOAD it before you start - FIXME- expand this descr. | If you use a Vanilla build you want to grab the custom libsal_uno.so with that compiled in and LD_PRELOAD it before you start - FIXME- expand this descr. | ||
| + | |||
| + | == Callgrind How-To == | ||
| + | |||
| + | There's a [http://tools.openoffice.org/profiling/callgrind-howto.html Callgrind How-To] at the OOo website. | ||
| + | |||
| + | TODO: move (!) its content here, not just copy but also remove there, so we don't end up with a fork. | ||
Revision as of 20:35, 16 November 2005
Making it work with OO.o
Some tools such as cachegrind require a patch to fix some stack layout problems: from Naren:
--- configure.in.orig 2005-06-07 14:21:44.142756416 -0700
+++ configure.in 2005-06-07 14:27:01.717477720 -0700
@@ -77,7 +77,7 @@
i?86)
AC_MSG_RESULT([ok (${host_cpu})])
VG_ARCH="x86"
- KICKSTART_BASE="0xb0000000"
+ KICKSTART_BASE="0x30000000"
ARCH_CORE_AM_CFLAGS="@PREFERRED_STACK_BOUNDARY@ -DELFSZ=32"
ARCH_TOOL_AM_CFLAGS="@PREFERRED_STACK_BOUNDARY@"
ARCH_CORE_AM_CCASFLAGS=""
Clearly it is necessary to run autoconf after applying that.
disabling the custom allocator
If you use ooo-build; export OOO_FORCE_SYSALLOC=1 before running, (this is built into linkoo's ooenv script).
If you use a Vanilla build you want to grab the custom libsal_uno.so with that compiled in and LD_PRELOAD it before you start - FIXME- expand this descr.
Callgrind How-To
There's a Callgrind How-To at the OOo website.
TODO: move (!) its content here, not just copy but also remove there, so we don't end up with a fork.
