PROBLEM:  (QAR 65009)    (Patch ID: OSF425-532)
********

A threaded program (one compiled with the -threads, -pthread, or equivalent
option or library) that is instrumented with the hiprof(5) profiling tool may
core dump during execution, if hiprof's -cputime option is used. For example:

> cc -threads pthread_test.c
> atom a.out -tool hiprof -env threads -toolargs="-threads -cputime"
> setenv LD_LIBRARY_PATH .
> ksh -v test.sh
./a.out.hiprof.threads
test.sh[5]: 29041 Memory fault(coredump)

PROBLEM:  (QAR 62693)    (Patch ID: OSF425-532)
********
A threaded program (one compiled with the -threads, -pthread, or equivalent
option or library) that is instrumented with the hiprof(5) profiling tool may
generate a grossly or subtly inaccurate profile if hiprof's -cputime option is
used. For example:

> cc -threads pthread_test.c
> atom a.out -tool hiprof -env threads -toolargs="-threads -cputime"
> setenv LD_LIBRARY_PATH .
> time ./a.out.hiprof.threads
0.22u 0.02s 0:00 27% 0+1k 50+19io 0pf+0w
> gprof -b a.out a.out.hiout | more

The total profiled cpu-time displayed by gprof may be larger than the total
cpu-time of the program displayed by the time command, or it may be more subtly
inaccurate such that the inaccuracy is not obvious but still significant.
The error is usually a few seconds for each occurrence of the problem.
Long-running programs may suffer repeated errors of this magnitude.

PROBLEM:  (QARs 62893, 62915, 66551)    (Patch ID: OSF425-532)
********
A non-threaded program that uses ldl_l/stl_c or ldq_l/stq_c instruction pairs
to implement test-and-set sequences may hang in an infinite loop or fail,
for example as the result of a time-out, if the program is instrumented with
the pixie(5) profiler. For example, commands like this

> atom a.out -tool pixie
> ./a.out.pixie

have been seen to result in the following Fortran RTL errors in different
Fortran applications, though the problem can affect any language:
 forrtl: severe (40): recursive I/O operation, unit 9, file unknown
 forrtl: severe (152): unresolved contention for DEC Fortran RTL global resource

PROBLEM:  (QAR 56108)    (Patch ID: OSF425-532)
********
A threaded program (one compiled with the -threads, -pthread, or equivalent
option or library) that is instrumented with the pixie(5) profiling tool may
hang or core dump during execution, if atom's -all or -incobj options are used
to instrument libpthreads.so, libpthread.so, libmach.so, libexc.so, or libc.so.
For example:

> cc -threads pthread_test.c
> atom a.out -tool pixie -env threads -all
> setenv LD_LIBRARY_PATH .
> ./a.out.pixie.threads
(hang or core dump)