Tom Lane wrote:
> Matthew Wakeling <matthew@flymine.org> writes:
>> I'm guessing my next step is to install a version of libc with debugging
>> symbols?
>
> Yeah, if you want to find out what's happening in libc, that's what you
> need.
Getting callgraph information from oprofile would also help. Although it
won't directly tell what function in libc is being called, you would see
where the calls are coming from, which is usually enough to guess what
the libc function is.
You can also get the oprofile data, including callgraph, into
kcachegrind, which is *very* helpful. Here's a script I use:
http://roberts.vorpus.org/~njs/op2calltree.py
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
