dapptrace, dappprof: DTrace's pid provider's "a.out" placeholder broken with -x evaltime=exec
| Originator: | hmijail | ||
| Number: | rdar://27733839 | Date Originated: | |
| Status: | Resolved: | ||
| Product: | OS X | Product Version: | 10.11.6 (15G31) |
| Classification: | Reproducible: | Always |
DTrace's pid provider uses a placeholder module named "a.out" to refer to probes coming from the running executable, as documented in Sun/Oracle's DTrace docs and used in the DTrace scripts included with OS X (like dapptrace and dappprof). The "a.out" placeholder fails to work when dtrace is called with the option -x evaltime=exec. This is exactly the way dapptrace and dappprof call dtrace, resulting in their functionality being broken. Example of a successful dtrace invokation: $ sudo dtrace -n 'pid$target:a.out:main:entry' -x evaltime=exec -c ./myexec dtrace: description 'pid$target:a.out:main:entry' matched 1 probe ... Steps to Reproduce: $ sudo dtrace -n 'pid$target:a.out:main:entry' -x evaltime=exec -c ./myexec dtrace: invalid probe specifier pid$target:a.out:main:entry: probe description pid81008:a.out:main:entry does not match any probes Expected Results: 1 dtrace probe should have been matched Actual Results: No probes are matched when using -x evaltime=exec
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!