0029-9039

Ÿ

 

0029-9040

 

 

 

 

-F

This flag can be used to turn off

lazy

reading

mode.

Turni

 

reading mode off forces the remote

dbx

sessions

to

read

 

 

table information at startup time. By

default,

lazy reading

 

 

Lazy reading mode

is

useful

when

debugging large

executable

 

when paging space is low. With lazy

reading mode on, only th

 

required symbol table information is read

 

upon

 

initialization

o

 

remote

dbx

sessions.

Because

all

symbol

table

information

is

 

 

at dbx startup time when in lazy reading

mode, local

variabl

 

related type information will not be

initially

available

for

f

 

defined in other files. The effect

of this can be seen

 

 

command, where instances of the specified

local

variable

may

 

found until the other files containing these instances are so

 

referenced.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

-h

Writes

the

pdbx usage to STDERR then exits.

This

includes

p

 

command

line

syntax

and

a

description

of

pdbx

options.

 

 

 

-I

Specifies

a

directory to

be

searched

for

an

executable's

 

This flag must be specified multiple

times to set multiple pa

 

pdbx

is

running,

this

list

can

be

overridden

on

a

group

or

 

 

basis

with

the

'use'

command.)

 

 

 

 

 

 

 

 

 

 

 

-xPrevents the dbx command from stripping _ (trailing underscore characters from symbols originating in FORTRAN source code. Thi flag enables dbx to distinguish between symbols which are i except for an underscore character, such as xxx and xxx_.

-tmpdirThis POE_option flag is normally associated with Visualization T trace collection. It specifies the directory to which outp written. For pdbx, it specifies the directory to which the startup files (.pdbxinit.process_id.task_id) are written for task. This is frequently local, and may be a shared direct and if its associated environment variable MP_TMPDIR is not se default location is /tmp.

Environment Variables:Because the pdbx command runs in the Parallel Operating Environment, it interacts with the same environment variables associated poe command. See the POE manual page for a description of these envi variables. As indicated by the syntax statements, you are also able command line options when invoking pdbx. Using these options will overrid setting of the corresponding environment variable, as is the case whe parallel program with the poe command.

0029-9039 Cannot read attach configuration file.

Explanation: pdbx could not read the attach configuration file, which is crea original POE job was started, and is removed when the job ends.

User Response:

1. Make sure the correct POE process id was used when invoking the debugge

2.Check the/tmp directory for the existence of a configuration file containi process id. (For example,/tmp/check.ppe.<poe pid>.attach.cfg ).

0029-9040 Cannot open attach configuration

file.

 

 

 

Explanation:

pdbx

was

unable

to

open

the attach

configuration file.

User Response:

 

 

 

 

 

 

1. Make

sure

that

the correct

POE

process id

was used when invoking the d

2.Check the/tmp directory for the existence of a configuration file containi process id. (For example, /tmp/check.ppe.for34192.attach.cfg ).

Chapter 2. pdbx Messages21

Page 37
Image 37
IBM GC28-1982-02 manual 0029-9040, Cannot read attach configuration file