Installation guide

.
.
.
(dbx) print r.a[511] 4
25
(dbx)
1 The where command displays the kernel stack followed by the user
program stack at the time of the crash. In this case, the kernel stack has 4
activation levels; the user program stack starts with the fifth level and
includes several recursive calls.
2
The up 8 command moves the debugging context 8 activation levels up
the stack to one of the recursive calls within the user program code.
3 The print r command displays the current value of the variable r,
which is a structure of array elements. Full symbolization is available for
the user program, assuming it was compiled with the -g option.
4 The print r.a[511] command displays the current value of array
element 511 of structure r.
5.6 Java Programming
The following note applies to Java programming.
5.6.1 Name Space Conflict Between Java and SVE
A file system conflict exists between Java and the System V Environment
(SVE) on Version 4.0 and later systems.
The problem arises because both Java and SVE use the file system path name
string /usr/bin/alpha for different purposes. Java creates
/usr/bin/alpha as a directory. SVE (specifically, the optional
SVEBCP4** Base Compatibility Package subset) creates
/usr/bin/alpha as a symbolic link to the
/usr/opt/svr4/usr/bin/alpha directory. The order in which these
applications are installed determines if the customer will experience a
problem. Here are three ways to avoid the problem:
• If SVE is already installed and the /usr/bin/alpha link exists, it is
safe to remove the link. The link is not used after the SVE installation
and for all other situations SVE will look for the directory location,
/usr/opt/svr/usr/bin/alpha. That directory will be found and
does not cause a conflict.
• If SVE has not yet been installed, Compaq recommends that SVE be
installed without the Inclusive View option. If Inclusive View is not
selected during SVE installation, the /usr/bin/alpha link will not be
needed during SVE installation.
5–10 Development Environment Notes