DTrace and function names

[O'Connor, Daniel]

> On 17 Jan 2015, at 02:07, John Baldwin <jhb at freebsd.org> wrote:
> On 1/15/15 9:55 PM, O'Connor, Daniel wrote:
>> 
>>> On 15 Jan 2015, at 00:47, John Baldwin <jhb at FreeBSD.org> wrote:
>>>> So it shows _some_ function names from libc but mostly not.. Is there a way to improve it?
>>> 
>>> Build with debug symbols?  For libc you can do that via:
>>> 
>>> % cd /usr/src/lib/libc
>>> % make cleandir
>>> % make obj
>>> # May want to use "-O -g" to reduce inlining
>>> % make DEBUG_FLAGS="-g" depend all install
>> 
>> OK, I guess I was thinking it wasn't necessary since some of the symbols showed up :(
> 
> Yeah, libc will always include symbols for the public functions it
> exports, but without -g you won't have symbols for any internal
> functions (and that's generally true of any shared library AFAIK).

Right, I guess it seems surprising so many internal functions show up..

I wonder if dtrace has an option to collapse the internal functions into their public parents (too much to hope for I imagine :)

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C