Date: Tue, 27 May 2008 01:23:58 +0000 From: John Birrell <jb@what-creek.com> To: freebsd-current@freebsd.org Subject: Re: dtrace and xorg-server problem on -current Message-ID: <20080527012358.GA16415@what-creek.com> In-Reply-To: <20080526171545.GA72427@wep4017.physik.uni-wuerzburg.de> References: <c21e92e20805260749m5e18e42p9df638976ee2e2b8@mail.gmail.com> <20080526151323.GB72053@wep4017.physik.uni-wuerzburg.de> <c21e92e20805260850i6b975cd7h8cdccad22d8fffd9@mail.gmail.com> <20080526171545.GA72427@wep4017.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 26, 2008 at 07:15:45PM +0200, Alexey Shuvaev wrote: > Well, the problem seems to be in the freebsd's implementation of dtrace. > Can some dtrace-guru say whether it is possible to fix the problem > on freebsd-side in a reasonable time? Or is it due to missing pid-provider > (or something else...) and then it is worthwhile disable dtrace support > in xorg-server? We don't support userland tracing yet, so the port will need to have the dtrace option turned off. -- John Birrell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080527012358.GA16415>