On Wed, Jun 13, 2012 at 9:33 PM, Ryan Goodfellow rgood...@eecs.wsu.edu wrote:
Hi FreeBSD community,
Today I downloaded and installed FreeBSD 9.0-RELEASE and followed the
directions from http://wiki.freebsd.org/DTrace to get DTrace up and
running. The output of DTrace instrumenting a simple
Ryan Goodfellow rgood...@eecs.wsu.edu wrote:
Today I downloaded and installed FreeBSD 9.0-RELEASE and followed the
directions from http://wiki.freebsd.org/DTrace to get DTrace up and
running. The output of DTrace instrumenting a simple program, however,
is not correct. The program is as
Top post.
File a PR and assign it to me (gnn) please.
I'm on vacation until Sunday but I am actively working on DTrace when I'm not
on vacation.
Best,
Geo
On Jun 14, 2012, at 02:53 , Fabian Keil wrote:
Ryan Goodfellow rgood...@eecs.wsu.edu wrote:
Today I downloaded and installed FreeBSD
Hi everyone, and thank you for the very prompt responses.
I did indeed compile world with CFLAGS+=-fno-omit-frame-poiner in my make.conf.
I will file the PR shortly.
Thank You
Ryan G
On Jun 14, 2012, at 9:00 AM, George Neville-Neil g...@neville-neil.com wrote:
Top post.
File a PR and
Hi FreeBSD community,
Today I downloaded and installed FreeBSD 9.0-RELEASE and followed the
directions from http://wiki.freebsd.org/DTrace to get DTrace up and running.
The output of DTrace instrumenting a simple program, however, is not correct.
The program is as follows:
// test.cc
Hi,
Would you please make sure you file a PR with exactly what you've just
listed above? You've gone into great detail here, so it should be easy
to reproduce.
What happens if you name it 'test.c' and compile it with cc (as a C
source) rather than C++?
Adrian
Hello fellows,
Is it Dtrace broken on HEAD?
root@controllerB:/sys/amd64/conf # dtrace -n 'syscall::open*:entry {
printf(%s %s,execname,copyinstr(arg0)); }'
*dtrace: invalid probe specifier syscall::open*:entry { printf(%s
%s,execname,copyinstr(arg0)); }: /usr/lib/dtrace/psinfo.d, line 37:
syntax
On Wed, May 30, 2012 at 6:37 AM, Marcelo Araujo araujobsdp...@gmail.com wrote:
Hello fellows,
Is it Dtrace broken on HEAD?
root@controllerB:/sys/amd64/conf # dtrace -n 'syscall::open*:entry {
printf(%s %s,execname,copyinstr(arg0)); }'
*dtrace: invalid probe specifier syscall::open*:entry
On Fri, 18 Feb 2011, Shawn Webb wrote:
Hey fellow current users,
Looks like dtrace is broken in current:
# dtrace -l -f acl dtrace: invalid probe specifier acl:
/usr/lib/dtrace/psinfo.d, line 37: syntax error near uid_t
Error messages along these lines almost always mean that the kernel
Hey fellow current users,
Looks like dtrace is broken in current:
# dtrace -l -f acl
dtrace: invalid probe specifier acl: /usr/lib/dtrace/psinfo.d, line 37:
syntax error near uid_t
Line 37 shows:
uid_t pr_uid; /* real user id */
Looks good to me, but why is dtrace complaining?
Disregard. I didn't have ksh93 installed. The handbook implies that it's
needed only for DTrace Toolkit, not DTrace itself. Installing ksh93 is
required for DTrace proper to work.
On Fri, Feb 18, 2011 at 9:36 PM, Shawn Webb latt...@gmail.com wrote:
Hey fellow current users,
Looks like dtrace
On Fri, 18 Feb 2011 21:50:59 -0700
Shawn Webb latt...@gmail.com wrote:
Disregard. I didn't have ksh93 installed. The handbook implies that
it's needed only for DTrace Toolkit, not DTrace itself. Installing
ksh93 is required for DTrace proper to work.
This cannot possibly be true.
% sudo
12 matches
Mail list logo
