If the process has children that called execve(), TotalView tries to determine each child’s executable. If TotalView cannot determine the executables for the children, you need to delete (kill) the parent process and start it under TotalView control.
To load a program, type the program’s name in the Program field. If you had previously loaded the program into TotalView, its name is remembered and you may find it on the pull-down list contained within this field. The name you enter can either be a full or relative path name.
If you enter just a file name, TotalView searches for the file in the directories you specified with the
File > Search Path command and in all the directories named in your
PATH environment variable.
If the program is to run on a different machine, you can select the computer’s name from the
On host field. If this machine isn’t on the list, select the
Add host button. After TotalView displays a dialog box, enter the machine’s name or an IP address.
By selecting the Enable memory debugging program, you tell TotalView to set up your program for Memory Debugging. Enabling it here is the same as enabling it within the Memory Debugger or using the Process Window’s
Debug> Enable Memory Debugging command.
The Enable memory debugging and
Halt on memory errors check boxes perform the same functions as the
Enable memory debugging and
On memory event, halt execution checkboxes do within the Advanced Options on MemoryScape’s Memory Debugging Options page. This is the equivalent of the basic Low setting.
The Enable ReplayEngine check box is visible only on Linux-x86 and Linux-86-64 platforms. If you do not have a license for ReplayEngine, enabling the check box has no effect and TotalView displays an error message when your program begins executing. Selecting this check box tells TotalView that it should instrument your code so that you can move back to previously executed lines.
After selecting Attach to process, TotalView shows a list of all your processes on the local host. If TotalView is connected to multiple hosts, the
On host field contains an additional
all hosts line. Select
all hosts to see the processes from all of the hosts, useful for attaching to a multiprocess program running on several different hosts.
In the displayed list, processes to which TotalView is already attached are shown in gray. The processes displayed in black are not currently running under TotalView control. To attach TotalView to any of these processes, select the process or processes, then press the
OK button.
Use the Filter by program or path field to view only the processes with a program or local path name matching the name you enter, helpful for finding a process or processes in which you are interested.
In some cases, the name provided to TotalView by your operating system may not be the actual name of the program. In this case, you will not be able to simply select the name and press the
OK button. Instead, you should
If you wish to attach to a multiprocess program, you can either pick up the processes one at a time or you can restart the program under TotalView control so that the processes are automatically picked up as they are forked. In most cases, this requires you to link your program with the
dbfork library, discussed in the
TotalView Reference Guide.
If the process you are attaching to is one member of a collection of related processes created with
fork() calls, TotalView asks if you want to also attach to all of its relatives. If you answer
yes, TotalView attaches to all the process’s ancestors, descendants, and cousins.
The information you specify when opening a core file is nearly identical to that you enter a regular process. It differs in that you also have to enter the name of the core file. You must enter a program name in the
Program field in addition to the
Core file field because TotalView cannot know if this program is actually associated with the process.
You can use the Browse button to search the file system for the core file.