If you are unable to find the information that you need in this guide, contact Arm support with a detailed report.
If possible, obtain a log file for the problem. To generate a log file,
either select the Help > Logging > Automatic menu option or start Arm® Forge with the
–debug and –log arguments:
$ ddt --debug --log=<logfilename>
$ map --debug --log=<logfilename>
<logfilename> is the name of the log file to generate.
Reproduce the problem using as few processors and commands as possible, and when complete, close the program as usual.
On some systems, this file might be quite large. If so, compress it
using a program such as gzip or bzip2 before sending it to support.
If your problem can only be replicated on large process counts, do not
use the Help > Logging > Debug menu item or the
–debug argument because these generate very large log files. Instead, use the menu option or the –log argument.
If you are connecting to a remote system, the log file is generated on the remote host and copied back to the client when the connection is closed. The copy does not happen if the target application crashes or the network connection is lost.
In these cases, the remote copy of the log file is in the tmp subdirectory
of the Arm configuration directory for the remote user account. The
directory is ~/.allinea, unless overridden by the ALLINEA_CONFIG_DIR environment variable.
Sometimes it might be helpful to illustrate your problem with a screenshot of the Arm® Forge main window. To take a screenshot, choose the Take Screenshot option under the Window menu. You are prompted for a file name when you save the screenshot.