is it likely that Dtrace will be coming to standard RELEASE kernels in
future?
i prefer not compile custom kernels for production servers but i do find the
system monitoring Dtrace affords rather handy.
--
View this message in context:
http://old.nabble.com/Dtrace-tp26562798p26562798.html
Sent
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'm looking for a faster way to get more verbose information about
dtrace function arguments.
For example.
Say, I want to know more about the funciton
syscall:freebsd32:connect:return. I'd start off by doing a listing:
# dtrace -lvf connect
-snip---
43723syscall
Does anyone know if it's likely DTrace will ever make it into the generic
RELEASEs?
Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd
Another strange behavior:
[Tab 1]
$ /bin/sleep 300 &
[1] 1806
[Tab 2]
$ sudo dtrace -n 'pid1806:sleep::entry'
$ 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, F
p, "Here I am at %s:%d.\n", __FILE__, __LINE__);
9fclose(fp);
10 }
[marca@freebsd9-0 ~]$ gcc test.c -o test
[marca@freebsd9-0 ~]$ sudo dtrace -n 'pid$target:test:main:entry' -c ./test
dtrace: description 'pid$target:test:main:entry' match
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
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
Hi,
Does anyone know what the status of dtrace being able to trace userland
processes is? I see there are few patches out there but am unsure of the
reliability etc.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman
In the last episode (Aug 15), Ashley Williams said:
> I'm looking for a faster way to get more verbose information about
> dtrace function arguments.
>
> For example.
>
> Say, I want to know more about the funciton
> syscall:freebsd32:connect:return. I'
>Does anyone know if it's likely DTrace will ever make it into the generic
> RELEASEs?
Maybe, at least in part. One of the developers has asked that the
hooks needed for dtrace be included by default in upcoming releases:
http://lists.freebsd.org/pipermail/freebsd-arch/2011-March/011
% httpd
-
Let's use dtrace to understand what's going on within 10 seconds
interval and normalize to 1 second:
-
% cat top-10-count-periodic.d
#pragma D option quiet
BEGIN
{
last = timestamp;
}
syscall:::entry
{
@func[execname] = count();
}
tick-10sec
{
trunc(@func, 10);
norma
On Tue, 20 Jul 2010 12:03:09 +0100
krad wrote:
> Does anyone know what the status of dtrace being able to trace
> userland processes is? I see there are few patches out there but am
> unsure of the reliability etc.
http://freebsdfoundation.blogspot.com/2010/06/dtrace-userland-pro
On 20 July 2010 13:02, Bruce Cran wrote:
> On Tue, 20 Jul 2010 12:03:09 +0100
> krad wrote:
>
> > Does anyone know what the status of dtrace being able to trace
> > userland processes is? I see there are few patches out there but am
> > unsure of th
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
Does anyone else see the following crash?
$ sh -c 'sleep 60& dtrace -P syscall -p $!'
dtrace: description 'syscall' matched 2092 probes
Assertion failed: (dpr != NULL), file
.../cddl/contrib/opensolaris/lib/libdtrace/common/dt_proc.c, line 751.
Exit 134
Also tri
er; I need LDAP
authentication and I want DTrace. (I also want GSSAPI, but that's another
discussion entirely).
(Why FreeBSD? DTrace and ZFS without the Oracle Solaris pricetag. Plus it's
a *NIX I haven't used yet.)
So I used csup to update to the latest ports, built postgresql90-serv
Hi guys,
I have a system running 10-CURRENT (r250217) which I've built Postgresql
9.2.4 with DTrace support enabled on & a VM running 9.1-STABLE (r250009)
which I'm unable to build it on.
On 10-CURRENT the problem is that dtrace -l does not list the postgresql
provider.
My mak
On 12/6/10 11:29 PM, "Dave Pooser" wrote:
> I used pkg_delete to
> remove the postgresql packages (server and client), recompiled the kernel to
> include DTrace and eliminate some unused drivers, updated loader.conf to
> bring up dtraceall at boot, did a make clean an
On Dec 14, 2010, at 9:01 PM, Dave Pooser wrote:
> Is there a better place I could/should be asking questions about PostgreSQL
> and DTrace on FreeBSD? Or is this combination still black magic at this
> point?
freebsd-ports@ is a reasonable alternative (since PostgreSQL is a port), but
Hi folks,
I have been using dtrace, and particularly procsystime, to measure
Samba system call usage stuff. This is what I get:
cs-cc1# ./procsystime -n smbd
Tracing... Hit Ctrl-C to end...
^C
Elapsed Times for processes smbd,
SYSCALL TIME (ns)
sysarch
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
Greetings all,
Has anyone else seen these errors during 9.1-stable boot...
Jan 16 08:12:05 sleipnir kernel: link_elf_obj: symbol cyclic_clock_func
undefined
Jan 16 08:12:05 sleipnir kernel: KLD file cyclic.ko - could not finalize loading
Jan 16 08:12:05 sleipnir kernel: KLD file dtrace.ko - can
23 matches
Mail list logo
