How do I get started analyzing the output of appcert?
Here is a three-step to procedure to follow: Step 1. See if appcert was able to check all of your binaries completely. If not, determine if incomplete checking was due to an inherent limitation in appcert (e.g., appcert can’t check calls to the C++ library libC), or to the runtime environment (e.g., LD_LIBRARY_PATH) not being properly set up. If necessary, rerun appcert.Step 2. Check for unbound symbols in shared object binaries. These may be due to your application’s using dlopen() to access the shared object; appcert has difficulty resolving the symbol bindings in that case (see the appcert man page for more information).Step 3. Check for private symbol usage. If appcert reports that your application uses a private symbol, but you can’t find any occurrence of it in your source code, then the reference is probably coming from a statically linked library; these cases can be ignored (though you should use dynamically linked libraries whenever possible). If you are actually using a priva
