I wondered if it might be because ps is linked to the magic "am I a
64-bit kernel"
or a "32-bit kernel" program (aka /usr/lib/isaexec) that magically
execs the
correct binary (at least on S10). You should still see what that does, I
would
think.
Well, that's not it. All you get if you start the real binary (on my
32-bit S10 vbox) is
__fsr:entry. You can see the libc functions, for example, but the
functions inside
ps are maddeningly hidden. Other programs (e.g., /usr/bin/cmp)
show the same behavior.
A bug in S10U7?
Jim
----
Adam Leventhal wrote:
That's strange -- I see lots of output. What operating system and
version are you running?
Adam
On Oct 28, 2009, at 3:58 PM, tester wrote:
how does one trace functions just in the binary (not including all
the libraries)
tracing ps gives this
# dtrace -n 'pid$target:ps::entry{}' -c "ps"
dtrace: description 'pid$target:ps::entry' matched 2 probes
PID TTY TIME CMD
9519 pts/4 0:00 vi
15706 pts/4 0:00 ps
15705 pts/4 0:02 dtrace
2137 pts/4 0:01 ksh
dtrace: pid 15706 has exited
CPU ID FUNCTION:NAME
19 59612 _start:entry
37 59614 _start:entry
thanks
--
This message posted from opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
