IBM GC28-1982-02 An attempt to, Call, Corresponding function for the specified executable file

2537-0061 Ÿ 2537-0065

2537-0061

An attempt to

access

call

count

information

in the

gmon.out

file,

string,

failed.

Explanation:

Internal

error.

Xprofiler

was

unable

to

access

the

call count

da

gmon.out

file. This problem should have been detected during an earlier sta

processing, instead

of

being

encountered

at

this

time. All

CPU

sampling

data i

be included in the information

in

the

main

display

and

all

report

windows,

bu

data will not. If thisgmon.outis

thefileonly being

loaded,

the

exclusion

of

this call

data will also affect the

placement

of

function

boxes

in

the

Function

Call

Tr

arcs

between

these boxes

NOT

to be

drawn.

User

Response:

Try reloading

your

files

again.

If

you

continue

to

get

this

gather

information

about

the

problem

and

follow local site

procedures

for

re

and

software

problems.

2537-0062

A

function

address

listed

in

the

gmon.out

file

string doesn't

map

to

the

corresponding function for the specified executable file.

Explanation:

While

processing

function

call count information, Xprofiler was unable

a function back to the appropriate

library file using the address listed

f

gmon.out

file. Therefore, some of the call count information was lost, and th

displayed

in

the

main

window

and some of the report windows will be incomple

possible reason for this problemg on.isout

thatfilethewas not created by the execu

file that you specified. Another

possibility

is

that

the

library

file asso

has

changed

sincegmon.theout

file

was

generated.

User

Response:

First,

verify

thatgmon.out this file

was

generated by the

specified

executable,

and if not, load it with the correct

executable file.

If

th

changed

since gmonthis.out

file

was

created,

re-compile

your

program,

and

then

e

to

generate

a gmonvalid.out

file.

2537-0063

The

second

non-comment

line

in

the

specified

configuration

file

string does

not

start

with

PROG=.

Explanation:

The

second

non-comment

line

in

an

Xprofiler

configuration

file

must

st

the

stringPROG=

;

otherwise,

it

is considered a syntax error.

User

Response:

Make

sure

the second non-comment line in the specified configurat

begins

with

the PROG=string,

starting

in

column

1.

2537-0064

Cannot

find

a

match

for

following

function(s)

in

the

program

that

is

currently

in

display:

string

Explanation:

A

function

name

in

the specified configuration file cannot find a

program

that

is

currently

in

display.

User

Response:

Make

sure

the

function

name is specified properly and the func

exist

in

the program currently

in

display.

2537-0065

The

following string(s)

in the

specified configuration file are not

recognized

configuration

keywords:

string

Explanation:

A keyword used in the specified configuration file is not a rec

configuration

keyword.

User

Response:

Make

sure

the

keyword

is

supported

by

the

Xprofiler

configura

Chapter 7. Xprofiler Messages183