Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Oct 2010 10:53:20 +0100
From:      =?UTF-8?Q?Istv=C3=A1n?= <leccine@gmail.com>
To:        Rui Paulo <rpaulo@freebsd.org>
Cc:        freebsd-current <freebsd-current@freebsd.org>, Garrett Cooper <gcooper@freebsd.org>
Subject:   Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT for userland apps
Message-ID:  <AANLkTikfvJNFW6fPq704Sm=OApgWCdWdOYqFn3jVq6jA@mail.gmail.com>
In-Reply-To: <28FFE6A7-0ECD-4454-9364-DC555327678E@freebsd.org>
References:  <AANLkTi=BTfcPYtO7Hby3dK7C7qiH2CXdThYyV9QBj8_T@mail.gmail.com> <DE0D21FF-0E8F-4993-87B0-69B7AA74861C@FreeBSD.org> <AANLkTins6w0znaw%2BvQ7M57cSXS1OK6aQ0KUyJMjD-ytq@mail.gmail.com> <7EC03A5E-61DA-46AB-95E1-1D844E10C735@FreeBSD.org> <AANLkTingZ1uQiC3TYaJtgQFG_m1HOAsOdCtRx4Aizj_i@mail.gmail.com> <D4CE1F20-02ED-4267-95D2-0199AEFA7C43@freebsd.org> <AANLkTinvBDQt-4Pk-GN3P1Wa20UTbr7OJaXiQeSD375u@mail.gmail.com> <FA2F29D4-F8E8-41A6-A471-DFE36C677B0D@freebsd.org> <AANLkTikZCUbwPF-grkAWQLVSL%2Bnm_NDBP%2B6ZLyYBNZxs@mail.gmail.com> <AANLkTimf%2B4xPLmYyrA%2B2GkYsRaNiLZjeAxEBL7MFd2Hk@mail.gmail.com> <AANLkTimFOKbix2bS0wQanGGv_jrysWm=kxu-FAEGd3g6@mail.gmail.com> <0B32E6BF-8CFE-4BC3-AFC8-EA77B1B5E8D7@freebsd.org> <AANLkTimqQESoHdzytUphBxTS8FYR6qiYeT3nfds2GJhU@mail.gmail.com> <28FFE6A7-0ECD-4454-9364-DC555327678E@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 19, 2010 at 10:33 AM, Rui Paulo <rpaulo@freebsd.org> wrote:

>
> On 19 Oct 2010, at 10:15, Istv=C3=A1n wrote:
>
> > wow, you go the point after couple of emails. better later than never,
> huh :)
>
> You sure are an amusing guy. Rude, but amusing :-)
>
>
thanks!


> >
> > you think adding pgsql to wheel might help? cc freebsd-security@ and se=
e
> their opinion about the topic.
>
> dof needs to inject the probes in /dev/dtrace/helper, so the user needs r=
w
> access to the /dev/dtrace/helper. I specifically added write access to th=
e
> wheel group for this.
>
>
and you think the only way to do that is to add pgsql to wheel group?!?

http://images.memegenerator.net/Troll-Face/ImageMacro/2337177/LOL-U-MAD-BRO=
.jpg



> >
> > i modified the permission of /dev/dtrace/helper instead but it gives th=
e
> following error still:
> >
> > dtrace DOF postgres: DTrace ioctl failed for DOF at 0x801c35000: Invali=
d
> argument
>
> This error usually means that there were no probes found in dof section o=
f
> the binary. Somehow they were not inserted correctly during the build sta=
ge.
>

you see, we are slowly getting there :)


>
> > do you mean /usr/ports/databases/postgresql90-server?
>
> Yes.
>
> >
> > I was rebuilding it with that switch, what now?
>
> Send me the build log, gzipped.
>

yes sir yes!

(and you are talking about ppl being rude)

what file do you need and which directory ___excatly___

btw. it would be beneficial for you as the DTrace maintainer of FreeBSD to
have your own environment and prove me that I am wrong since you are happil=
y
tracing on your own box, it is just the lame user who is not able to do tha=
t
:)

your own words:

"Tracing and instrumenting userland programs is very important because it
allows the understanding of what's going on, especially on highly complex
systems such as databases, web servers, and language interpreters. Since
DTrace on FreeBSD now has the ability to instrument both the kernel and the
userland program, you can get very meaningful data on how your program is
behaving and why."

So instead of fixing my problem on my box, fix it for everybody and update
the wiki with the process if you have a chance. As of now, I consider
FreeBSD as a non-supported platform for DTrace since I spent almost 2 days
to get it working without success and it is definitely less effort to spin
up a (Open)Solaris instance to debug performance issue. Let me know if you
get it working in the future.

thank you in advance.

--=20
the sun shines for all

http://blog.l1x.me



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