https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193109
--- Comment #3 from Garrett Cooper <[email protected]> --- (In reply to Mark Johnston from comment #2) > (In reply to Mark Johnston from comment #1) > > This type of error is almost always the result of some sort of > > misconfiguration. A couple of things to check: > > > > 1. Is kern.bootfile set to the correct path for the running kernel? > > 2. Is there CTF data present in the kernel? > > The latter can be checked with something like 'ctfdump /boot/kernel/kernel'. Yup, that's ok: % [ -n "$(ctfdump $(kenv kernelname))" ] && echo "I have CTF in the kernel" I have CTF in the kernel > If nothing interesting turns up, try running a dtrace command manually on > the system in question, e.g. "dtrace -n 'fbt::kern_ioctl:entry'" or so. If > it fails with the same error, try running it again with the DTRACE_DEBUG > environment variable set to 1 and paste the output. That command works (and prints out info) $ sudo dtrace -n 'fbt::kern_ioctl:entry' dtrace: description 'fbt::kern_ioctl:entry' matched 1 probe CPU ID FUNCTION:NAME 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 1 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 1 34641 kern_ioctl:entry ^C $ I don't know how the preprocessing and resolution of C typedefs is handled with dtrace, but it seems like the issue is there and not in the actual dtrace runtime... -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
