Filter
Top Products
0029-2002 0029-2014
0029-2002 Could not add the groups events (breakpoints or tracepoints) to task:
number
, because this task is RUNNING.
Explanation: Since the task was RUNNING and not available for debug commands, pdbx
could not add the group events (breakpoints or tracepoints) for this task. It is possible to
continue but the group breakpoints will not have been set for this task.
User Response: Issue the group list or tasks command to check the state of the tasks.
Create a new group after all of the tasks of interest have stopped RUNNING and are under
debugger control.
0029-2003 Breakpoint or tracepoint:
string
could not be set by pdbx on task:
number
.
Explanation: The remote dbx was unable to set a breakpoint or tracepoint.
User Response: Make sure the requested breakpoint or tracepoint was valid. Use the
status command to see what pdbx events have been set. Issue the pdbx where command
to find out where the program is on each node.
0029-2004
string
is ambiguous on one or more of the tasks in the current context.
Also, the response from whatis
string
varies from task to task. The
following grouping of tasks would give each group the ability to resolve
the symbol consistently:
Explanation: If a symbol, typically a function, is found to be ambiguous, pdbx issues a
menu to the user that allows him to select the instance(s) to which the command ( such as
stop in, list, or func ) is applied. To simplify the user interface, the parallel debugger requires
that all tasks in the partition have a consistent view of the ambiguous symbol, since pdbx
can display only one selection menu for a context.
User Response: Issue the whatis command to make sure the symbol in question is
resolved in the current context. This message is also followed by a table that suggests a set
of groups, each of which would resolve the symbol in the same way. Using these or similar
groups, you could issue the same command by changing the context as desired.
0029-2005 The network connection from pdbx or pedb to task:
number
failed.
Explanation: An error was encountered when pdbx or pedb attempted to read or write
using a socket connection to the task. pdbx or pedb will no longer have any control over
this task.
User Response: The debugger can continue after a task loses contact with the home
node. Under certain circumstances, you might choose to continue debugging using the
remaining tasks for some period of time.
0029-2013 Debugger attached and ready.
Explanation: All of the specified tasks have been attached, and you are able to start
debugging.
User Response: None. This is an informational message.
0029-2014 Internal Error: non-zero status:
number
returned from pm_respond().
Explanation: Internal Error: The main communication control section of the home node
portion of pdbx has indicated a failure.
User Response: Restart pdbx, verify that your job runs correctly under poe and that poe
is correctly installed and configured for your id. If the problem persists, gather information
about it and follow local site procedures for reporting hardware and software problems.
Chapter 2. pdbx Messages 5