I'm using DTrace's anonymous tracing feature to trace through device 
drivers at boot time. With Solaris 10 Update 6 B5, I was unable to trace 
fbt based calls  from the sd attach point. The error messages from the 
console are:

NOTICE: enabling probe 0 (fbt::sdattach:entry)
NOTICE: enabling probe 1 (fbt:::)
NOTICE: enabling probe 2 (fbt::sdattach:return)
NOTICE: enabling probe 3 (dtrace:::ERROR)
do_relocate: bad strndx 0
do_relocations: /kernel/drv/amd64/scsa2usb do_relocate failed
scsa2usb error doing relocations
fcp error reading symbols
do_relocate: bad strndx 0
do_relocations: /kernel/misc/amd64/fctl do_relocate failed
fctl error doing relocations
<plenty of error messages related to undefined symbols>

I'd like to know if anyone else is encountering problems with anonymous 
tracing. The only way I've been able to recover is to reinstall the OS 
since this keeps repeatedly crashing at boot time. I saw 6703055 has 
been filed although my crashes appear to be different because of the 
relocation errors.

Thanks,

Sri
_______________________________________________
dtrace-discuss mailing list
[email protected]

Reply via email to