Simple dtraces not working

[msabramo]

Shouldn't this work?

marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo dtrace -n 'pid$target:::entry' -c '/bin/uname'
aux[0]: type=32
aux[1]: type=33
aux[2]: type=16
aux[3]: type=6
aux[4]: type=17
aux[5]: type=3
aux[6]: type=4
aux[7]: type=5
aux[8]: type=7
aux[9]: type=8
aux[10]: type=9
aux[11]: type=11
aux[12]: type=12
aux[13]: type=13
aux[14]: type=14
aux[15]: type=23
aux[16]: type=25
aux[17]: type=31
aux[18]: type=15
aux[19]: type=0
in Pupdate_maps (check for 64b maps!)
in Pupdate_maps (check: pr_mapname is big enough PRMAPSZ=64)
rd_new:rd_new
rd_loadobj_iter
proc-stub:rd_event_enable
proc-stub:rd_errstr err=26
Build symtab /usr/sbin/dtrace
found section .interp
found section .note.ABI-tag
found section .note.gnu.build-id
found section .hash
found section .gnu.hash
found section .dynsym
found section .dynstr
found section .gnu.version
found section .gnu.version_r
found section .rel.dyn
found section .rel.plt
found section .init
found section .plt
found section .text
found section .fini
found section .rodata
found section .eh_frame_hdr
found section .eh_frame
found section .ctors
found section .dtors
found section .jcr
found section .dynamic
found section .got
found section .got.plt
found section .data
found section .bss
found section .comment
found section .debug_aranges
found section .debug_pubnames
found section .debug_info
found section .debug_abbrev
found section .debug_line
found section .debug_frame
found section .debug_str
found section .debug_loc
found section .debug_ranges
found section .shstrtab
found section .symtab
found section .strtab
plt at 0x9ef5cd0
sym_by_name_binary: NOT found _PROCEDURE_LINKAGE_TABLE_
Pxlookup_by_name 'main' a.out 0x9ef5814 0x9ef4994
sym_by_name_binary: found main
dtrace: invalid probe specifier pid$target:::entry: "/usr/lib/dtrace/sched.d", line 60: no symbolic type information is available for kernel`dtrace_cpu_id: Invalid argument
dt_proc_destroy flags=37748737
User defined signal 1

[msabramo]

or these?

marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probe
dtrace: failed to compile script ./probe: "/usr/lib/dtrace/sched.d", line 60: no symbolic type information is available for kernel`dtrace_cpu_id: Invalid argument
marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probeall
dtrace: invalid probe specifier fbt:::entry{ @[probefunc] = count(); }: "/usr/lib/dtrace/sched.d", line 60: no symbolic type information is available for kernel`dtrace_cpu_id: Invalid argument

[dtrace4linux]

for your first issue - proc dtracing is incredibly fragile and a lot of debug junk is displayed.

for the latter, remove /usr/lib/dtrace - if the system doesnt build the ctf binary tools, then you get these undefs.

both are TODO items (ctf requires a private and working libdwarf lib - most older releases have broken versions).

[msabramo]

I still can't get tests/probe to work:

marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probe
dtrace: failed to compile script ./probe: "/usr/lib/dtrace/sched.d", line 60: no symbolic type information is available for kernel`dtrace_cpu_id: Invalid argument
marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo rm -rf /usr/lib/dtrace
marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probe
dtrace: failed to compile script ./probe: line 8: 'pid0' does not contain a valid pid
marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ cd ..
marca@ubuntu:~/src/dtrace4linux/newlinux$ make all
...
install -m 644 -o root build/linux*.ctf ""/usr/lib/dtrace
install -m 644 -o root etc/io.d ""/usr/lib/dtrace
install -m 644 -o root etc/sched.d ""/usr/lib/dtrace
install -m 644 -o root etc/unistd.d ""/usr/lib/dtrace
scripts/mkinstall.pl -o=""/usr/lib/dtrace
marca@ubuntu:~/src/dtrace4linux/newlinux$ cd tests
marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probe
dtrace: failed to compile script ./probe: "/usr/lib/dtrace/sched.d", line 60: no symbolic type information is available for kernel`dtrace_cpu_id: Invalid argument

I got tests/probeall to work though:

marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo ./probeall
^C
...
  _spin_unlock_irqrestore                                        8583
  find_next_bit                                                  8641
  restore_all                                                    8645
  restore_nocheck                                                8645
  __ticket_spin_lock                                            14249
  __ticket_spin_unlock                                          14278
  kstat_irqs_cpu                                                15104

and this too, which is pretty cool:

marca@ubuntu:~/src/dtrace4linux/newlinux/tests$ sudo dtrace -n 'proc::: { printf("%s", execname) }'
dtrace: description 'proc::: ' matched 3 probes
CPU     ID                    FUNCTION:NAME
  0     48                          :create bash
  0     49                           :start bash
  0     48                          :create tpvmlp
  0     49                           :start tpvmlp
  0     50                            :exit tpvmlp
  0     48                          :create python
  0     49                           :start python
  0     48                          :create sh
  0     49                           :start sh
  0     50                            :exit ls
  0     50                            :exit sh
  0     50                            :exit python
^C

This all makes me think that we need a dtrace4linux manual or maybe a GitHub Wiki (here's a sample) or GitHub Page so that we can document what kinds of things you can do with it. What do you think?

[grosser]

I think I got something similar ...

2.0.0p247 :002 > Object::Profiler.track { puts "asdada" }
proc-stub:rd_event_enable
proc-stub:rd_errstr err=26
dtrace: failed to compile script /usr/local/rvm/gems/ruby-2.0.0-p247/gems/object_profiler-0.0.3/lib/object/profiler/probes/object_create.d: line 1: probe description ruby*:::object-create does not match any probes

^C

[dtrace4linux]

I dont have time to look at this in the next few weeks (I might do, but
really not many promises).

If you run an app which exposes probes, /proc/dtrace/fbt will show the
probes available and you can grep for the ones you are after.
/proc/dtrace/trace may show some useful messages when the app is run
declaring the probes.

On 26 July 2013 22:08, Michael Grosser notifications@github.com wrote:

I think I got something similar ...

2.0.0p247 :002 > Object::Profiler.track { puts "asdada" }
proc-stub:rd_event_enable
proc-stub:rd_errstr err=26
dtrace: failed to compile script /usr/local/rvm/gems/ruby-2.0.0-p247/gems/object_profiler-0.0.3/lib/object/profiler/probes/object_create.d: line 1: probe description ruby*:::object-create does not match any probes

^C

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-21648278
.