Date: Sat, 17 Jan 2015 09:21:09 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: DTrace and function names Message-ID: <EC3BBA9A-1FC2-4221-9093-43C7F577D71E@dons.net.au> In-Reply-To: <54B9302A.7070002@FreeBSD.org> References: <ED72FCF4-7917-4EA9-8331-A940F70E2578@dons.net.au> <54B67A60.2000708@FreeBSD.org> <D0363778-8D7D-4A67-98FB-A4F978F20D4F@dons.net.au> <54B9302A.7070002@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Jan 2015, at 02:07, John Baldwin <jhb@freebsd.org> wrote: > On 1/15/15 9:55 PM, O'Connor, Daniel wrote: >>=20 >>> On 15 Jan 2015, at 00:47, John Baldwin <jhb@FreeBSD.org> wrote: >>>> So it shows _some_ function names from libc but mostly not.. Is = there a way to improve it? >>>=20 >>> Build with debug symbols? For libc you can do that via: >>>=20 >>> % cd /usr/src/lib/libc >>> % make cleandir >>> % make obj >>> # May want to use "-O -g" to reduce inlining >>> % make DEBUG_FLAGS=3D"-g" depend all install >>=20 >> OK, I guess I was thinking it wasn't necessary since some of the = symbols showed up :( >=20 > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC3BBA9A-1FC2-4221-9093-43C7F577D71E>