On Tue, Nov 27, 2007 at 10:50:17AM -0800, James McIlree wrote:
> I doubt that the jump table is being caused by calling through a
> function pointer.
The code sequence for a function pointer call is similar to that of a
jump table. At one point we tried to distinguish the two, but found th
Hello,
I'm trying to debug an issue with rpc.metad on Solaris 10, basecally I
believe the failure path is
- svc_init
-- check_sys
--- check_host
strcmp(hostname, mynode())
It seems that for some reason hostname and mynode didn't match then I
would like to use dtrace to show the argument o
fds[ fd ].fi_pathname is the magical thing it seems.
Thanks Angelo!
For example:
syscall::read:entry
{
printf("s\n", fds[arg0].fi_pathname);
}
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolari
Hey Paul:
You can use the fds inlined translator to get to the file name.
For example to see all the files that are being read(2) in the system
dtrace -n syscall::read:entry'{trace(fds[arg0].fi_pathname)}'
Let me know if you need more details
-Angelo
On Nov 29, 2007, at 12:32 PM, Paul van de
an active process that opens and closes files all the time reuses file
descriptors. Therefor a certain fd value might not correspond with that same fd
value (in that same process) a couple of seconds later.
What structure is available in a DTrace program from within a read,write,lseek
and other
