Hello,
I''ve done this several times in the past but a co-worker is having
problems
getting anonymous tracing to work:
dtrace -A -m su
and we see updated /kernel/drv/dtrace.conf and fbt and dtrace forceloads
added to /etc/system. Upon reboot the following errors occur (note that
we are running snv_66):
{0} ok boot disk
Boot device: /pci at 0/pci at 0/pci at 2/scsi at 0/disk at 0 File and args:
SunOS Release 5.11 Version snv_66 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
NOTICE: enabling probe 0 (:su::)
NOTICE: enabling probe 1 (dtrace:::ERROR)
This sounds like what was discussed in bug 5069032 but I can''t
find a newer reference than that bug.
Any ideas?
Thanks,
Kevin.
--
This message posted from opensolaris.org
Kevin, I certainly could be missing something here, but I don''t see the error. The notices appear normal. What do you get when consume the anonymous data with "dtrace -ae" ? Chip Kevin Crowe wrote:> Hello, > > I''ve done this several times in the past but a co-worker is having problems > getting anonymous tracing to work: > > dtrace -A -m su > > and we see updated /kernel/drv/dtrace.conf and fbt and dtrace forceloads > added to /etc/system. Upon reboot the following errors occur (note that > we are running snv_66): > > {0} ok boot disk > Boot device: /pci at 0/pci at 0/pci at 2/scsi at 0/disk at 0 File and args: > SunOS Release 5.11 Version snv_66 64-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > NOTICE: enabling probe 0 (:su::) > NOTICE: enabling probe 1 (dtrace:::ERROR) > > This sounds like what was discussed in bug 5069032 but I can''t > find a newer reference than that bug. > > Any ideas? > > Thanks, > Kevin. > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org >
Thanks to Chip and Andrew for responding to me. I don''t recall ever getting the line of output on boot with "ERROR" in it before: NOTICE: enabling probe 1 (dtrace:::ERROR) The machine continues to boot with no further dtrace related output and upon logging in we do get some dtrace data (see below) just apparently not from the very start of the driver loading since asyopen() is not one of the first routines to run: # dtrace -ae CPU ID FUNCTION:NAME 9 39878 asyopen:entry 9 39892 asy_program:entry 9 39902 async_msint:entry 9 39903 async_msint:return 9 39893 asy_program:return ...(etc)... A further suggestion was to set modload to see module load info to help determine what was loading and in which order it was loading to see if that could be related to the ''ERROR'' perhaps. However, since this isn''t my problem to debug, as long as my co-worker gets what he needs from the dtrace data, my interest level in debugging it further wanes. Thanks all, Kevin. -- This message posted from opensolaris.org
On Fri, Jun 22, 2007 at 11:24:08AM -0700, Kevin Crowe wrote:> Thanks to Chip and Andrew for responding to me. I don''t recall ever getting the line > of output on boot with "ERROR" in it before: > NOTICE: enabling probe 1 (dtrace:::ERROR)The DTrace library automatically creates an enabling of the dtrace:::ERROR probe for you so that it can report errors encountered during the execution of your script (e.g. a NULL-pointer dereference). This is why you''re seeing that probe enabled. Adam -- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl