Currently dtrace.sh runs and then leaves a dtrace process running in the
background that must be manually killed. It needs to be refactored to
automatically terminate dtrace after it has finished logging the input java
executable.
I have already tried two approaches:
1. Terminate dtrace after the java process terminates
Terminating dtrace after java has finished running doesn't guarantee that
dtrace has flushed it's log buffer to stdout.
2. Use dtrace -c 'cmd'
Passing the java command into dtrace doesn’t work. I feel like this should
work somehow, so this approach is probably worth reexploring.
Original issue reported on code.google.com by T.101.JV on 7 Feb 2012 at 1:16
Original issue reported on code.google.com by
T.101.JVon 7 Feb 2012 at 1:16