Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Sep 2012 13:04:52 -0400
From:      Chris Nehren <apeiron+freebsd-stable@isuckatdomains.net>
To:        freebsd-stable@freebsd.org
Subject:   Re: Userland dtrace broken?
Message-ID:  <20120913170452.GF5302@isuckatdomains.isuckatdomains.net>
In-Reply-To: <503E129B.7070607@icritical.com>
References:  <503E129B.7070607@icritical.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--PGNNI9BzQDUtgA2J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 29, 2012 at 14:01:15 +0100 , Matt Burke wrote:
> Following http://wiki.freebsd.org/DTrace/userland on 9.1-RC1, the example
> fails to work as demonstrated:
>=20
> # dtrace -s pid.d -c test
> dtrace: script 'pid.d' matched 2 probes
> CPU     ID                    FUNCTION:NAME
>   1  59284                       main:entry
> dtrace: pid 25479 exited with status 1
>=20
> #
>=20
>=20
> Also, I get hangs when trying to do pretty much anything with the pid:::e=
ntry
>=20
> # dtrace -n 'pid$target::malloc:entry' -c 'echo x'
> dtrace: description 'pid$target::malloc:entry' matched 2 probes
> xCPU     ID                    FUNCTION:NAME
>   1  59311                     malloc:entry
> load: 0.43  cmd: dtrace 63737 [running] 8.93r 1.60u 4.19s 35% 25072k
> load: 0.88  cmd: echo 63738 [running] 45.10r 2.27u 18.75s 47% 1452k
> load: 1.19  cmd: dtrace 63737 [running] 70.32r 12.14u 33.27s 64% 25072k
>=20
> # procstat -k 63737 63738
>   PID    TID COMM             TDNAME           KSTACK
> 63737 101505 dtrace           -                mi_switch
> sleepq_catch_signals sleepq_timedwait_sig _sleep do_wait
> __umtx_op_wait_uint_private amd64_syscall Xfast_syscall
> 63737 111024 dtrace           -                <running>
> 63738 101657 echo             -                mi_switch
> thread_suspend_switch ptracestop cursig ast doreti_ast
>=20
>=20
> I have previously tried using dtrace on 9.0R, but it was insta-panic. Is
> there anything I may have missed here?
>=20
>=20
>=20
> make.conf:
> STRIP=3D
> CFLAGS+=3D-fno-omit-frame-pointer
> WITH_CTF=3D1
>=20
> kernel config:
> include         GENERIC
> ident           DTRACE
>=20
> makeoptions     DEBUG=3D"-g"
> makeoptions     WITH_CTF=3D1
> options         KDTRACE_FRAME
> options         KDTRACE_HOOKS
> options         DDB_CTF
> options         DDB
>=20

Relevant to my interests, too. I've followed the instructions on the
wiki / in the handbook (on 9.0/9.1-PRE) and only receive error messages.
Is DTrace supposed to be working properly on 9.x, or is it still
experimental?

It's nice to say that FreeBSD nominally supports DTrace, but if it
doesn't actually work then it needs to be labelled as such. I am fine
with it being experimental if that's the case, but saying so would help
manage expectations a lot better.

--=20
Thanks and best regards,
Chris Nehren

--PGNNI9BzQDUtgA2J
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBAgAGBQJQUhIzAAoJEB3ywRGrHAnQjpoP/3/ae5cR8wBOhsJRBHxZn9KX
oceYxm7LQYg+wBPlln6IiJwaUU1hTd2naAMxZcEACHNFB5NlFaohl2MIKTYVqZh7
wmBc3FzVJB+woIW1CETM2gqgFdDAQF4cSwEVICst2u/f95M4H5SxT58ID/m3V5ks
3D1wl72TPRkqGeJyGgOHuasljq9NLqnZgyLMYerVzrSdBARCpXyGLZe7ukeonMK0
9co8BW17rs+xz1vAvZihkQnJTwiCE+3Fi3N+PVdhMKK3f9C8fHyHrgn5WFbpcRGE
mw2D289dEQy1sc3yhneFsrkwZ7b9QktZ8cRw3VS1cD/cWbmTa5DeeCSWMd6+9t73
7gv5TkS43cxIhndMcjI9AMi9ZVYqUFGD9V94D0lqo1XEkTYDrVEU9+D8THL8Meqd
rNyZ+VhYLzi8N+OdwiWiFXVI2A4dv5rgwdy5XL9NoesmrNYxHRCcPWiM5I+AF/q9
+QeyPMELwHpsFzBZXdjZ9xlGxmSK7nhmiyJWxmvt2xQBMPi3YSpShdnRM76DHQh6
g+0KNC8Vk+np7rdTZrQg0Tqs2L34uQip+c584qoEo5upd07tYmwuFvvr8l0xgjVz
2vTzHpA3SGV4r36msWmVDAvlgM+PCXbNuSOQ0zG9sk9DRdYYv8DEgTl/set54AvP
oy+9wjVpi6O4Aa9fRg8a
=HDF9
-----END PGP SIGNATURE-----

--PGNNI9BzQDUtgA2J--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120913170452.GF5302>