On Tue, Feb 28, 2012 at 12:24 PM, Marc Abramowitz wrote:
> Here's another way to cause a kernel panic:
>
> [marca@freebsd9-0 ~]$ sudo kldload dtraceall
> ...
> [marca@freebsd9-0 ~]$ sudo dtrace -n 'pid$target:test:main:entry' -c
> ./test
> dtrace: description 'pid$target:test:main:entry' matched 1
On Tue, Feb 28, 2012 at 12:58 PM, Rui Paulo wrote:
> Please file a PR. These are problems that we have to fix.
I submitted a PR for the kernel panic at
http://www.freebsd.org/cgi/query-pr.cgi?pr=165541
Marc
___
freebsd-questions@freebsd.org mailing l
y'
> $ echo $?
> 158
>
> [Tab 1]
> [1]+ Killed: 9 /bin/sleep 300
>
> Something seems very wrong that DTrace is killing processes and causing
> kernel panics.
>
> Marc
>
> On Mon, Feb 27, 2012 at 10:22 PM, Marc Abramowitz wrote:
>
>&
eb 27, 2012 at 10:22 PM, Marc Abramowitz wrote:
> I'm using FreeBSD 9.0 on amd64 in VMware Fusion and trying to DTrace
> userland programs. I think I must be doing something wrong.
>
> I recompiled my kernel and world, following the instructions at
> http://wiki.freeb
I'm using FreeBSD 9.0 on amd64 in VMware Fusion and trying to DTrace
userland programs. I think I must be doing something wrong.
I recompiled my kernel and world, following the instructions at
http://wiki.freebsd.org/DTrace and I've read
http://wiki.freebsd.org/DTrace/userland:
The
I upgraded my box so that I can rock the userland DTrace probes. I have been
following the example at: http://wiki.freebsd.org/DTrace/userland
When I am ready to build my test probe, I run 'make' as the example shows. The
result of that is the following:
cc -O2 -pipe -fno-omit-fra
hello freebsd gurus...
i'm currently using FreeBSD 9.0-CURRENT-201101...
dtrace is enable and working
[root@ ~]# dtrace -l | tail -5
41473profile tick-1000
41474profile tick-5000
41475
