ADC Home>Reference Library>Reference>Mac OS X>Mac OS X Man Pages |
Highly proficient in Adobe InDesign CC, Adobe Illustrator CC, Adobe Photoshop CC / Adobe Flash / Software as well as Mac OS X / Keynote / Drawing / sketch-up. Brooke Straiton. Brooke Straiton. This Mac application is an intellectual property of com.fourmach. This app can be installed on Mac OS X 10.8 or later. The program lies within Design & Photo Tools, more precisely Viewers & Editors. This program's bundle is identified as com.fourmach.startrails. Our antivirus scan shows that this Mac download is clean.
This document is a Mac OS X manual page. Manual pages are a command-line technologyfor providing documentation. You can view these manual pages locally using theman(1) command.These manual pages come from many different sources, and thus, have a variety of writingstyles. For more information about the manual page format, see the manual page for manpages(5). |
Please try submitting your feedback later.
Your input helps improve our developer documentation.
I am running OSX desktops coming from Linux background. We cross-develop software both on OSX and Linux. I am familiar of debugging system issues on Linux using strace command and now I had to try something similar on OSX. strace prints out system calls a running application makes so you can see “inside” the application and see where it crashes, hangs, etc.
OSX doesn’t have strace, but has its equivalent dtrace which originates from Solaris and I believe it has replaced OSX ktrace, truss etc. commands since OSX 10.5 Leopard.
Here are brief instructions how I tracked down a non-working Subversion svn up command. svn was correctly updating some repositories, but not others and just hung which means it probably hung on some system call.
Turns out dtrace itself is a very low level framework which its own programming language. I just want to dump the system calls. So there exist an utility called dtruss for this purpose.
But the first attempt failed:
You could solve this by running dtruss as root, but we really don’t want to do that. You can enable normal user execution for dtruss / dtrace with the following command:
Now we dtruss get output:
… and there it hangs. Unknown command “failure”. In the end this all was not very helpful and I decided just selfupdate Macports and take clean checkout.