On Tue, Aug 26, 2008 at 12:57:46AM -0700, Thomas Mohme wrote: > Unfortunately "dtrace -l -n pid[i]nnnn[/i]:a.out::entry" gives me this: > > dtrace: failed to match pid[i]nnnn[/i]:stub.exe::entry: No probe matches > description > > > while "nm stub.exe | fgrep FUNC" gives me this: > [snip] > > From this I conclude that the needed symbols aren't stripped from our > module(s). So I expect DTrace to "see" at least functions "main", "action", > etc. > > So mdb sees not only the "standard"-libraries, but also our modules, which > DTrace seems to refuse > > Any suggestions are welcome.
Hey Thomas, Can you explain a bit more about how zones fits into the picture (what works or doesn't work from what zones on processes in what zones, etc)? Also, can you send me a private email with the output of the following invocation: dtrace -l -n pid123:a.out:entry -x debug Thanks. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
