Letting vxgetcore find debugging data automatically (the easiest method)


Letting vxgetcore find debugging data automatically (the easiest method)
Prev	About collecting application and daemon core data for debugging	Next

If you do not know the location of the core file or if you do not want vxgetcore to stop for any user prompts, you can run vxgetcore with the -a option.

In this mode, vxgetcore searches through a list of known core file locations, starting with the current working directory. It selects the latest core file that it finds in any of these directories. Then, vxgetcore automatically finds the associated binary file, library file, and any available debugging data automatically. In this method, vxgetcore gathers information without prompting you. If you intend to run vxgetcore as a command within a script, this option is also the one to use.

Note:

Because you do not specify the core file name or binary file name with this option, vxgetcore makes its best effort to find the correct files. If vxgetcore finds more than one core file or binary file, it chooses the latest file in the first directory it finds. If you do not think that these are the correct files, and you know the location and names of the files, run vxgetcore specifying the core file and binary file names.

Before you run vxgetcore, contact Symantec Technical Support and get a case ID for your issue. You'll need to include the case ID in the tar file name before you send it to Symantec.

To let vxgetcore find data automatically

If you do not know the location of the core file, enter the following command. vxgetcore looks for a core file in the current working directory, followed by other core locations. If you use the -C option, substitute your information for the given syntax:
```
# /opt/VRTSspt/vxgetcore/vxgetcore -a [-C Symantec_case_ID]
```
vxgetcore finds the core file and searches a predetermined list of directories for the associated binary file, library files, and other debugging data. It then creates a tar file in this format:
```
/tmp/VRTSgetcore.xxxx/coreinfo.CASEID.hostname.date_time.tar.gz
```
Review the system output. vxgetcore lists the core file name, binary file name, and the other files it gathers. If these are not the file you intended, rerun the command and specify the file names.
In the tar file creation message, note the checksum of the new tar file.
(Optional) If you did not specify your case ID on the command in step 2, rename the tar file name to include your case ID number.
FTP the file to your local FTP site. See the following TechNote for FTP site details:
http://www.symantec.com/docs/TECH66995
Contact your Symantec Technical Support representative and tell them the checksum and the FTP site to which you uploaded the file.

If you know the location of the core file, you can use the -c option along with the -a option. In this case, vxgetcore uses the specified core file and automatically finds the debugging information that is related to this core file. If you are running vxgetcore as part of a script, the script does not pause for user input.