Next: When all else fails, Previous: Problems with make, Up: Troubleshooting [Contents][Index]
After coNCePTuaL is configured, compiled, built, and installed, there is still the chance that coNCePTuaL-generated executables fail to run. This section addresses some common problems and presents their solutions.
As a quick tip, a very conservative way to run a coNCePTuaL program is with the NCPTL_NOFORK environment variable set to ‘1’, the NCPTL_CHECKPOINT environment variable set to ‘0’, and with --no-trap=1-63 on the command line. Such usage should work around some of the most common—and some of the hardest to diagnose—problems that may impact a coNCePTuaL program. Read the corresponding sections (Miscellaneous mysterious hangs or crashes; Extremely noisy measurements; and, Keeping programs from dying on a signal) for information about the drawbacks of each of the preceding settings.
• ``cannot open shared object file'': | Preventing problems with libncptl.so | |
• Miscellaneous mysterious hangs or crashes: | Programs die inexplicably | |
• Extremely noisy measurements: | Data exhibits excessive variability | |
• Keeping programs from dying on a signal: | Handling unexpected terminations | |
• ``Unaligned access'' warnings: | What these mean and how to prevent them | |
• ``Unable to determine the OS page size'': | Specifying page sizes | |
• Invalid timing measurements: | coNCePTuaL’s timer is completely wrong | |
• ``TeX capacity exceeded'': | Problems drawing complex diagrams with latex_vis | |
• Bad bounding boxes from latex_vis: | Generated pictures are truncated |
Next: When all else fails, Previous: Problems with make, Up: Troubleshooting [Contents][Index]