tag:blogger.com,1999:blog-8336326562741944626.post3088284981727228086..comments2023-11-03T01:34:26.403-07:00Comments on CRiSP, DTrace, and other technobabble: another dtrace delayCrisp Editorhttp://www.blogger.com/profile/14144625547464350210noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8336326562741944626.post-48450930934059963302015-12-04T09:09:58.705-08:002015-12-04T09:09:58.705-08:00Having trouble finding the *right* place to reply ...Having trouble finding the *right* place to reply to this post... <br /><br />I got past the 'old_rsp' issue without the dtrace_kmem driver & thought I'd share (perhaps it may be useful in diagnosis). Running the 'make all' I received the 'old_rsp' error. Thinking I might post the output to Issues on GitHub, I ran the following to display the kernel version and error messages at the same time:<br /><br />uname -a;make all | egrep -e 'BUILD_DIR|ERROR'<br /><br />The build completed successfully, as did the 'make load', and 'make install'. I tested the output on a little program I wrote:<br /><br />[root@lenx100e dtrace-20151106]# dtrace -n 'syscall:::entry /execname == "filecopy"/ { @[probefunc] = count(); }'<br />dtrace: description 'syscall:::entry ' matched 652 probes<br />^C<br /><br /> exit_group 1<br /> close 2<br /> write 1597794<br /> read 1597795<br />[root@lenx100e dtrace-20151106]# <br /><br />OS = CentOS 6.7<br />Kernel version = 2.6.32-573.8.1.el6.x86_64.<br /><br />Thanks for working on this port! This is excellent work.Richhttps://www.blogger.com/profile/02530399673948191774noreply@blogger.comtag:blogger.com,1999:blog-8336326562741944626.post-34492492855325605822015-12-02T09:09:00.818-08:002015-12-02T09:09:00.818-08:00Quite interesting post...if you do not mind my ask...Quite interesting post...if you do not mind my asking, does dtrace support the latest kernel 4?Rui F Ribeirohttps://www.blogger.com/profile/15255721077488270696noreply@blogger.comtag:blogger.com,1999:blog-8336326562741944626.post-86960785880890640602015-12-02T09:08:02.272-08:002015-12-02T09:08:02.272-08:00This comment has been removed by the author.Rui F Ribeirohttps://www.blogger.com/profile/15255721077488270696noreply@blogger.com