================================================================================
PowerUX NightView*
Version 4.3
Release Notes
Harris Computer Systems Corporation
1. Introduction
NightView is a general-purpose, source-level debugger for Ada, C, C++,
and Fortran, with support for multiple processes.
NOTE: NightView is supported on Series 4000 and Series 5000 systems
running CX/UX(TM) and on systems based on the PowerPC(TM) running
PowerUX(TM). This version of the release notes is for PowerUX.
NightView 4.3 features include:
o Support for C++.
o Support for type conversions in Ada expressions.
NOTE: Installation procedures for this product are slightly different
from those for other Concurrent products. Please read the
"Installation" section of these release notes before attempting to
install this product, and carefully follow the installation
instructions.
NOTE: In these release notes, chapter and section references are to
the NightView User's Guide, unless stated otherwise.
__________
* These release notes cover the following products: NightView
- 1 -
PowerUX NightView 4.3 Release Notes
2. Documentation
The following table lists the documentation available with this
release:
___________________________________________
| Manual Name Pub. Number |
|___________________________|______________|
| NightView User's Guide | 0890395-120 |
| NightView Pocket Reference| 0890475-010 |
| NightView Release Notes | 0890395-4.3P|
|___________________________|______________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
3. Prerequisites
Prerequisites for NightView Version 4.3 are as follows:
3.1 Software Prerequisites
o PowerUX release 2.1.1 or later.
o PowerUX 2.2 or later is required to use the following features on
a process waiting in an interruptible system service (e.g.,
server_block or fbswait):
- the attach command
- the Stop button in the Debug Window
- the stop command
Under PowerUX 2.1.1 the debugger indicates that the process is
stopped, but the process is not stopped.
o Base patch base-004 on PowerUX 2.2, so privileges P_DEV and
P_OWNER are inherited by the dialogue shell. Patch es-001 is
also required if you are running the Enhanced Security package.
These fixes are included in PowerUX 3.1.
- 2 -
Release Notes 4.3 PowerUX NightView
Under PowerUX 2.1.1, P_DEV and P_OWNER are not propagated to the
dialogue shell.
o An X(TM) server is required if you are using NightView's
graphical user interface. (The X server may be built into the
bitmapped display device.)
o The X Window System(TM), Version 11.
o Elan License Manager(TM). See the "Installation" section of
these release notes for details.
For more information about configuring your system to support
NightView, see appendix B, "System Resource Requirements", in the
NightView User's Guide.
3.2 Hardware Prerequisites
o Any system based on the PowerPC running PowerUX.
o A bitmapped display device, such as an X terminal, if you are
using NightView's graphical user interface.
4. Installation
The NightView product is installed as a software package using the
Software Packaging Tools. Please refer to the chapter "Installing
Add-On Software" in the System Administration Manual, Volume 1 (Pub.
No. 0890429), the PowerUX Release Notes (Pub. No. 0890454), and the
pkgadd(1M) command for instructions on software installation.
NightView may be installed in either the root directory or elsewhere.
When you run pkgadd(1M) to install NightView, you are prompted to
enter the name of the directory for installation. If you want to
install in the root directory, just press the RETURN key at the
prompt. Otherwise, enter the name of the directory where you want
NightView installed. If this directory does not exist, the
installation procedures attempt to create it for you.
NightView must be run with the Elan License Manager. Follow the steps
in the "Obtaining Licenses" section of the Elan License Manager
Release Notes (0891055); the feature alias is NightView. If you are
debugging Ada, then you need an additional license. The Elan feature
alias to debug Ada is NightView_Ada. If you are not already running
the Elan License Manager, if you do not have a copy of the Elan
License Manager Release Notes, or if you need a license key, contact
Concurrent Software Distribution at 1-800-666-5405.
- 3 -
PowerUX NightView 4.3 Release Notes
If your site has multiple license servers, and you need to indicate a
server on a particular system, you can set the environment variable
POWERWORKS_ELMHOST to the name of server's system before invoking
NightView. If you used to set the environment variable
HARRIS_ELMHOST, set POWERWORKS_ELMHOST instead. For more information,
see the Elan License Manager Release Notes (0891055).
5. Cautions
5.1 Ada Tasks, Threads and Lightweight Processes
NightView 4.3 does not yet have direct support for Ada tasks, threads
or lightweight processes. However, the select-context command
provides some support. See section 7.10.4, "select-context".
5.2 Ada Support
Many Ada features are supported, but some are not. See section
3.10.1.1, "Ada Expressions".
5.3 Unimplemented Features
Several features described in the NightView User's Guide are not
implemented in this release. These include:
o Remote debugging
o Parameters to login
o These commands: pause, return, wait
o Programming constructs
Some of the manual appendixes are not yet written.
5.4 Breakpoint Command Streams
The current implementation of breakpoint command streams does not
include protection against concurrent access of data structures
internal to the debugger. Avoid referencing other processes within
breakpoint command streams. In practice, this is rarely a problem.
- 4 -
Release Notes 4.3 PowerUX NightView
5.5 Fortran 77 Arrays
There is currently a problem with Fortran 77 arrays passed as formal
arguments. The compiler generates a temporary variable to optimize
references to the array. This temporary variable is then used in
place of the original array argument. If the original array argument
is not used later in the routine, then the lifetime of the argument is
very short and its value is discarded. If you try to use the debugger
to reference the argument later in the routine, the results are
undefined. You can do two things to avoid running into this problem:
o Use the array later in the routine. For example, pass the array
as an argument to another routine. This extends the lifetime of
the original argument.
o Use the debugger to look at the array at the first executable
line of the routine. The value of the original argument probably
still exists at this point.
5.6 Scroll Bars
Some users have had a problem using the scroll bars in the graphical
user interface. When the up-arrow button on a scroll bar is clicked,
the window scrolls the length of the entire window contents, rather
than just one line. This problem is caused by an inappropriate X
resource, which has apparently been copied from one user to another in
much the same way as $HOME/.profile files are often copied:
*XmScrollBar*translations: <Btn1Down>: Select()
You should remove this resource from your $HOME/.Xdefaults or whatever
other means you use for setting X resources. This resource affects
any Motif(TM) application, not just NightView.
5.7 Accessing Variables While in Prologue of Subprogram
Because the compilers generate line-number information for code that
comprises the prologue of a subprogram, you may inadvertently set an
eventpoint or stop your program at such a location. The prologue is
the code that the compiler generates to set up the execution
environment for a subprogram; until that code completes execution, the
environment is incomplete. Attempts to access variables while in the
context of the prologue may result in errors from NightView or may
result in erroneous values.
- 5 -
PowerUX NightView 4.3 Release Notes
If you suspect such a problem, you can determine whether you are in
the prologue by doing the following:
o Stop the program at the point where the referencing problem
occurs.
o Enter the command info frame.
o If the output from this command says something like "Could not
obtain frame description information", then you are probably
stopped in the prologue.
To try and avoid this problem, do not set an eventpoint on the lines
containing a subprogram heading. If you want to set the eventpoint at
the beginning of the subprogram, use the unit_name (for Ada) or
function_name form of location specifier, rather than a file_name and
line_number. See section 7.1.2, "Location Specifiers".
5.8 Shared Objects
For core files, NightView cannot always find correct stack description
information (tdesc) for shared objects. This problem occurs when the
shared objects are built without position-independent code. This
problem can cause NightView to display the wrong results for any
routine other than the most recently called routine. For example, a
backtrace command may print the wrong information, or an up command
may fail. This is true for any release of NightView, not just 4.3.
This is not a problem for running processes, only for core files.
We recommend that you build shared objects with position-independent
code if you plan to debug programs that use them. For C and Fortran,
use the -Zpic option. See cc(1) or f77(1). For Ada, use -sm shared
or -sm both. See "Shared Libraries and Shared-Objects" on page 3-12
of the HAPSE Reference Manual (Pub. No. 0890288-100).
5.9 Demo Program
The demo program, /usr/lib/NightView/nview-demo, gets an error when it
tries to display the title window, when run with version 5.3 of the X
Window System package. The error message is:
xwud: XWD file format version mismatch.xwud: Error => exiting.
UX:zcat: ERROR: /usr/lib/NightView/nv.xwd: Broken pipe
This does not affect the rest of the demo. A later version of the X
Window System package fixes the problem. This problem affects any
release of NightView, not just 4.3.
- 6 -
Release Notes 4.3 PowerUX NightView
6. Product Description
6.1 New Features in This Release
6.1.1 C++_Support
NightView 4.3 supports C++ direct compilation (invoked with cc++). As
with previous releases, 4.3 supports C++ compilation to C (invoked
with CC, or with cc++ --mode=cgen) only indirectly. See appendix F,
"Debugging C++" and section 3.10.1.3, "C++ Expressions".
6.1.2 Type_Conversions_in_Ada_Expressions
Type conversions are supported as defined for the Ada language, and
using the same syntax as that of the language (i.e.
type_mark(expression)). See section 3.10.1.1, "Ada Expressions".
6.2 Changes from Previous Releases
6.2.1 Ada_Exceptions
This release fixes a bug with looking up complex Ada exception names
in a handle command. See section 7.8.12, "handle".
6.2.2 Ada_Standard_Package
4.3 fixes some problems with finding names in the Ada package
standard.
6.2.3 Type_Checking_Actual_Parameters
NightView is now more lenient when checking the types of actual
parameters to Ada subprograms. See section 3.10.1, "Expression
Evaluation".
- 7 -
PowerUX NightView 4.3 Release Notes
6.2.4 Listing_Ada_Functions
4.3 fixes a bug with listing Ada functions in separately compiled
subunits. See section 7.5.1.1, "list".
6.2.5 Debug_Source_Selection_Dialog_Box
The debug source selection dialog box now displays fully qualified
function names for Ada and C++. Any regular expression is applied
only to the final component of the name. See section 9.3.13.2, "Debug
Source Selection Dialog Box".
6.2.6 Expressions
4.3 fixes problems with various expression operators:
o the Ada or else and C || operators.
o C assignment operators such as +=.
o comparison operators.
See section 3.10.1, "Expression Evaluation".
6.2.7 Conditional_Eventpoints
4.3 fixes a bug with undefined external references in eventpoint
conditional expressions. See section 3.6.1, "Eventpoints".
6.2.8 Patched_Gotos_and_Restart
Some patched gotos were not handled correctly by restart. This
release fixes that problem. See section 7.7.4, "patchpoint" and
section 3.6.3, "Restarting a Program".
6.2.9 Fortran_INTEGER*1
Earlier releases of NightView had difficulty distinguishing between
Fortran's CHARACTER, INTEGER*1 and LOGICAL*1 types. That is fixed in
this release.
- 8 -
Release Notes 4.3 PowerUX NightView
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 9 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 3
4. Installation................................................... 3
5. Cautions....................................................... 4
5.1 Ada Tasks, Threads and Lightweight Processes.............. 4
5.2 Ada Support............................................... 4
5.3 Unimplemented Features.................................... 4
5.4 Breakpoint Command Streams................................ 4
5.5 Fortran 77 Arrays......................................... 5
5.6 Scroll Bars............................................... 5
5.7 Accessing Variables While in Prologue of Subprogram....... 5
5.8 Shared Objects............................................ 6
5.9 Demo Program.............................................. 6
6. Product Description............................................ 7
6.1 New Features in This Release.............................. 7
6.1.1 C++ Support........................................ 7
6.1.2 Type Conversions in Ada Expressions................ 7
6.2 Changes from Previous Releases............................ 7
6.2.1 Ada Exceptions..................................... 7
6.2.2 Ada Standard Package............................... 7
6.2.3 Type Checking Actual Parameters.................... 7
6.2.4 Listing Ada Functions.............................. 8
6.2.5 Debug Source Selection Dialog Box.................. 8
6.2.6 Expressions........................................ 8
6.2.7 Conditional Eventpoints............................ 8
6.2.8 Patched Gotos and Restart.......................... 8
6.2.9 Fortran INTEGER*1.................................. 8
7. Direct Software Support........................................ 9
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerUX NightViewTM
Version 4.3
Release Notes
0890395-4.3P
December 1996
_________________________________________________________________
Trademark Acknowledgments
CX/UX is a trademark of Concurrent Computer
Corporation.
Elan License Manager is a trademark of Elan Computer Group, Inc.
Motif is a trademark of Open Software Foundation,
Inc.
NightView is a trademark of Concurrent Computer
Corporation.
PowerPC is a trademark of IBM Corp.
PowerUX is a trademark of Concurrent Computer
Corporation.
X is a trademark of X Consortium, Inc.
X Window System is a trademark of X Consortium, Inc.
return to index
================================================================================
================================================================================
PowerMAX OS NightView*
Version 4.3.1
Release Notes
Harris Computer Systems Corporation
1. Introduction
NightView is a general-purpose, source-level debugger for Ada, C, C++,
and Fortran, with support for multiple processes.
NOTE: NightView is supported on Series 4000 and Series 5000 systems
running CX/UX(TM) and on systems based on the PowerPC(TM) running
PowerMAX OS(TM). This version of the release notes is for PowerMAX
OS.
NightView 4.3.1 features include:
o Support for Ada protected objects.
o Support for Ada child units.
NOTE: Installation procedures for this product are slightly different
from those for other Concurrent products. Please read the
"Installation" section of these release notes before attempting to
install this product, and carefully follow the installation
instructions.
NOTE: In these release notes, chapter and section references are to
the NightView User's Guide, unless stated otherwise.
__________
* These release notes cover the following products: NightView
- 1 -
PowerMAX OS NightView 4.3.1 Release Notes
2. Documentation
The following table lists the documentation available with this
release:
_____________________________________________
| Manual Name Pub. Number |
|___________________________|________________|
| NightView User's Guide | 0890395-130 |
| NightView Pocket Reference| 0890475-010 |
| NightView Release Notes | 0890395-4.3.1P|
|___________________________|________________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
3. Prerequisites
Prerequisites for NightView Version 4.3.1 are as follows:
3.1 Software Prerequisites
o PowerMAX OS release 4.1 or later.
o An X server is required if you are using NightView's graphical
user interface. (The X server may be built into the bitmapped
display device.)
o The X Window System(TM), Version 11.
o Elan License Manager(TM). See the "Installation" section of
these release notes for details.
For more information about configuring your system to support
NightView, see appendix B, "System Resource Requirements", in the
NightView User's Guide.
3.2 Hardware Prerequisites
o Any system based on the PowerPC running PowerMAX OS.
o A bitmapped display device, such as an X terminal, if you are
using NightView's graphical user interface.
- 2 -
Release Notes 4.3.1 PowerMAX OS NightView
4. Installation
The NightView product is installed as a software package using the
Software Packaging Tools. Please refer to the chapter "Installing
Add-On Software" in the System Administration Manual, Volume 1 (Pub.
No. 0890429), the PowerMAX OS Release Notes (Pub. No. 0890454), and
the pkgadd(1M) command for instructions on software installation.
NightView may be installed in either the root directory or elsewhere.
When you run pkgadd(1M) to install NightView, you are prompted to
enter the name of the directory for installation. If you want to
install in the root directory, just press the RETURN key at the
prompt. Otherwise, enter the name of the directory where you want
NightView installed. If this directory does not exist, the
installation procedures attempt to create it for you.
NightView must be run with the Elan License Manager. Follow the steps
in the "Obtaining Licenses" section of the Elan License Manager
Release Notes (0891055); the feature alias is NightView. If you are
debugging Ada, then you need an additional license. The Elan feature
alias to debug Ada is NightView_Ada. If you are not already running
the Elan License Manager, if you do not have a copy of the Elan
License Manager Release Notes, or if you need a license key, contact
Concurrent Software Distribution at 1-800-666-5405.
If your site has multiple license servers, and you need to indicate a
server on a particular system, you can set the environment variable
POWERWORKS_ELMHOST to the name of server's system before invoking
NightView. If you used to set the environment variable
HARRIS_ELMHOST, set POWERWORKS_ELMHOST instead. For more information,
see the Elan License Manager Release Notes (0891055).
5. Cautions
5.1 Ada Tasks, Threads and Lightweight Processes
NightView 4.3.1 does not yet have direct support for Ada tasks,
threads or lightweight processes. However, the select-context command
provides some support. See section 7.10.4, "select-context".
- 3 -
PowerMAX OS NightView 4.3.1 Release Notes
5.2 Ada Support
Many Ada features are supported, but some are not. See section
3.10.1.1, "Ada Expressions".
5.3 Unimplemented Features
Several features described in the NightView User's Guide are not
implemented in this release. These include:
o Remote debugging
o Parameters to login
o These commands: pause, return, wait
o Programming constructs
Some of the manual appendixes are not yet written.
5.4 Breakpoint Command Streams
The current implementation of breakpoint command streams does not
include protection against concurrent access of data structures
internal to the debugger. Avoid referencing other processes within
breakpoint command streams. In practice, this is rarely a problem.
5.5 Fortran 77 Arrays
There is currently a problem with Fortran 77 arrays passed as formal
arguments. The compiler generates a temporary variable to optimize
references to the array. This temporary variable is then used in
place of the original array argument. If the original array argument
is not used later in the routine, then the lifetime of the argument is
very short and its value is discarded. If you try to use the debugger
to reference the argument later in the routine, the results are
undefined. You can do two things to avoid running into this problem:
o Use the array later in the routine. For example, pass the array
as an argument to another routine. This extends the lifetime of
the original argument.
o Use the debugger to look at the array at the first executable
line of the routine. The value of the original argument probably
still exists at this point.
- 4 -
Release Notes 4.3.1 PowerMAX OS NightView
5.6 Scroll Bars
Some users have had a problem using the scroll bars in the graphical
user interface. When the up-arrow button on a scroll bar is clicked,
the window scrolls the length of the entire window contents, rather
than just one line. This problem is caused by an inappropriate X
resource, which has apparently been copied from one user to another in
much the same way as $HOME/.profile files are often copied:
*XmScrollBar*translations: <Btn1Down>: Select()
You should remove this resource from your $HOME/.Xdefaults or whatever
other means you use for setting X resources. This resource affects
any Motif(TM) application, not just NightView.
5.7 Accessing Variables While in Prologue of Subprogram
Because the compilers generate line-number information for code that
comprises the prologue of a subprogram, you may inadvertently set an
eventpoint or stop your program at such a location. The prologue is
the code that the compiler generates to set up the execution
environment for a subprogram; until that code completes execution, the
environment is incomplete. Attempts to access variables while in the
context of the prologue may result in errors from NightView or may
result in erroneous values.
If you suspect such a problem, you can determine whether you are in
the prologue by doing the following:
o Stop the program at the point where the referencing problem
occurs.
o Enter the command info frame.
o If the output from this command says something like "Could not
obtain frame description information", then you are probably
stopped in the prologue.
To try and avoid this problem, do not set an eventpoint on the lines
containing a subprogram heading. If you want to set the eventpoint at
the beginning of the subprogram, use the unit_name (for Ada) or
function_name form of location specifier, rather than a file_name and
line_number. See section 7.1.2, "Location Specifiers".
- 5 -
PowerMAX OS NightView 4.3.1 Release Notes
5.8 Shared Objects
For core files, NightView cannot always find correct stack description
information (tdesc) for shared objects. This problem occurs when the
shared objects are built without position-independent code. This
problem can cause NightView to display the wrong results for any
routine other than the most recently called routine. For example, a
backtrace command may print the wrong information, or an up command
may fail. This is true for any release of NightView, not just 4.3.1.
This is not a problem for running processes, only for core files.
We recommend that you build shared objects with position-independent
code if you plan to debug programs that use them. For C and Fortran,
use the -Zpic option. See cc(1) or f77(1). For Ada, use -sm shared
or -sm both. See "Shared Libraries and Shared-Objects" on page 3-12
of the HAPSE Reference Manual (Pub. No. 0890288-100).
5.9 Demo Program
The demo program, /usr/lib/NightView/nview-demo, gets an error when it
tries to display the title window, when run with version 5.3 of the X
Window System package. The error message is:
xwud: XWD file format version mismatch.xwud: Error => exiting.
UX:zcat: ERROR: /usr/lib/NightView/nv.xwd: Broken pipe
This does not affect the rest of the demo. A later version of the X
Window System package fixes the problem. This problem affects any
release of NightView, not just 4.3.1.
6. Product Description
6.1 New Features in This Release
6.1.1 Ada_Protected_Objects
NightView 4.3.1 supports Ada protected objects. You can refer to
protected objects in commands such as print and set, and you can set
eventpoints in the routines associated with the objects. However, you
cannot call the routines associated with protected objects from the
print and set commands or from monitorpoint, patchpoint or tracepoint
expressions or in eventpoint conditional expressions.
- 6 -
Release Notes 4.3.1 PowerMAX OS NightView
6.1.2 Ada_Child_Units
NightView 4.3.1 supports Ada child units.
6.1.3 set-patch-area-size
You can change the size of the regions NightView creates in your
process with the set-patch-area-size command. See section 7.4.5.11,
"set-patch-area-size". The info dialogue command prints the current
values. See section 7.12.1.17, "info dialogue".
6.2 Changes from Previous Releases
6.2.1 Mmap_regions
NightView 4.3.1 uses mmap for most of the regions it creates in your
process. This reduces the shared memory requirements on the system
and improves debugger performance during a fork. See appendix B,
"System Resource Requirements" and appendix H, "Implementation
Overview".
6.2.2 Monitorpoints
4.3.1 fixes a problem with setting multiple monitorpoints at once.
See section 7.7.7, "monitorpoint".
6.2.3 Performance_Enhancements
4.3.1 processes symbolic debugging information faster than earlier
releases.
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
- 7 -
PowerMAX OS NightView 4.3.1 Release Notes
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 8 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 2
4. Installation................................................... 3
5. Cautions....................................................... 3
5.1 Ada Tasks, Threads and Lightweight Processes.............. 3
5.2 Ada Support............................................... 4
5.3 Unimplemented Features.................................... 4
5.4 Breakpoint Command Streams................................ 4
5.5 Fortran 77 Arrays......................................... 4
5.6 Scroll Bars............................................... 5
5.7 Accessing Variables While in Prologue of Subprogram....... 5
5.8 Shared Objects............................................ 6
5.9 Demo Program.............................................. 6
6. Product Description............................................ 6
6.1 New Features in This Release.............................. 6
6.1.1 Ada Protected Objects.............................. 6
6.1.2 Ada Child Units.................................... 7
6.1.3 set-patch-area-size................................ 7
6.2 Changes from Previous Releases............................ 7
6.2.1 Mmap regions....................................... 7
6.2.2 Monitorpoints...................................... 7
6.2.3 Performance Enhancements........................... 7
7. Direct Software Support........................................ 7
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerMAX OS NightViewTM
Version 4.3.1
Release Notes
0890395-4.3.1P
February 1997
_________________________________________________________________
Trademark Acknowledgments
CX/UX is a trademark of Concurrent Computer
Corporation.
Elan License Manager is a trademark of Elan Computer Group, Inc.
Motif is a trademark of Open Software Foundation,
Inc.
NightView is a trademark of Concurrent Computer
Corporation.
PowerMAX OS is a trademark of Concurrent Computer
Corporation.
PowerPC is a trademark of IBM Corp.
X Window System is a trademark of The Open Group.
return to index
================================================================================
================================================================================
PowerMAX OS NightView*
Version 4.3.2
Release Notes
Harris Computer Systems Corporation
1. Introduction
NightView is a general-purpose, source-level debugger for Ada, C, C++,
and Fortran, with support for multiple processes.
NOTE: NightView is supported on Series 4000 and Series 5000 systems
running CX/UX(TM) and on systems based on the PowerPC(TM) running
PowerMAX OS(TM). This version of the release notes is for PowerMAX
OS.
NightView 4.3.2 features include:
o Auto-frame mode.
o A variant of the handle command to deal with unhandled Ada
exceptions.
o A z option to the x command, to print in hexadecimal and ASCII.
o Performance improvements. Large C++ programs will benefit the
most.
NOTE: Installation procedures for this product are slightly different
from those for other Concurrent products. Please read the
"Installation" section of these release notes before attempting to
install this product, and carefully follow the installation
instructions.
__________
* These release notes cover the following products: NightView
- 1 -
PowerMAX OS NightView 4.3.2 Release Notes
NOTE: In these release notes, chapter and section references are to
the NightView User's Guide, unless stated otherwise.
2. Documentation
The following table lists the documentation available with this
release:
_____________________________________________
| Manual Name Pub. Number |
|___________________________|________________|
| NightView User's Guide | 0890395-140 |
| NightView Pocket Reference| 0890475-010 |
| NightView Release Notes | 0890395-4.3.2P|
|___________________________|________________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
3. Prerequisites
Prerequisites for NightView Version 4.3.2 are as follows:
3.1 Software Prerequisites
o PowerMAX OS release 4.1 or later.
o An X server is required if you are using NightView's graphical
user interface. (The X server may be built into the bitmapped
display device.)
o The X Window System(TM), Version 11R6 with Motif(TM) 2.1.
o Elan License Manager(TM). See the "Installation" section of
these release notes for details.
For more information about configuring your system to support
NightView, see appendix B, "System Resource Requirements", in the
NightView User's Guide.
- 2 -
Release Notes 4.3.2 PowerMAX OS NightView
3.2 Hardware Prerequisites
o Any system based on the PowerPC running PowerMAX OS.
o A bitmapped display device, such as an X terminal, if you are
using NightView's graphical user interface.
4. Installation
The NightView product is installed as a software package using the
Software Packaging Tools. Please refer to the chapter "Installing
Add-On Software" in the System Administration Manual, Volume 1 (Pub.
No. 0890429), the PowerMAX OS Release Notes (Pub. No. 0890454), and
the pkgadd(1M) command for instructions on software installation.
NightView may be installed in either the root directory or elsewhere.
When you run pkgadd(1M) to install NightView, you are prompted to
enter the name of the directory for installation. If you want to
install in the root directory, just press the RETURN key at the
prompt. Otherwise, enter the name of the directory where you want
NightView installed. If this directory does not exist, the
installation procedures attempt to create it for you.
NightView must be run with the Elan License Manager. Follow the steps
in the "Obtaining Licenses" section of the Elan License Manager
Release Notes (0891055); the feature alias is NightView. If you are
debugging Ada, then you need an additional license. The Elan feature
alias to debug Ada is NightView_Ada. If you are not already running
the Elan License Manager, if you do not have a copy of the Elan
License Manager Release Notes, or if you need a license key, contact
Concurrent Software Distribution at 1-800-666-5405.
If your site has multiple license servers, and you need to indicate a
server on a particular system, you can set the environment variable
POWERWORKS_ELMHOST to the name of server's system before invoking
NightView. If you used to set the environment variable
HARRIS_ELMHOST, set POWERWORKS_ELMHOST instead. For more information,
see the Elan License Manager Release Notes (0891055).
5. Cautions
- 3 -
PowerMAX OS NightView 4.3.2 Release Notes
5.1 Ada Tasks, Threads and Lightweight Processes
NightView 4.3.2 does not yet have direct support for Ada tasks,
threads or lightweight processes. However, the select-context command
provides some support. See section 7.10.4, "select-context".
5.2 Ada Support
Many Ada features are supported, but some are not. See section
3.10.1.1, "Ada Expressions".
5.3 Unimplemented Features
Several features described in the NightView User's Guide are not
implemented in this release. These include:
o Remote debugging
o Parameters to login
o These commands: pause, return, wait
o Programming constructs
Some of the manual appendixes are not yet written.
The unimplemented tracefile= option to the set-trace command has been
removed from the manual.
5.4 Breakpoint Command Streams
The current implementation of breakpoint command streams does not
include protection against concurrent access of data structures
internal to the debugger. Avoid referencing other processes within
breakpoint command streams. In practice, this is rarely a problem.
5.5 Fortran 77 Arrays
There is currently a problem with Fortran 77 arrays passed as formal
arguments. The compiler generates a temporary variable to optimize
references to the array. This temporary variable is then used in
place of the original array argument. If the original array argument
is not used later in the routine, then the lifetime of the argument is
very short and its value is discarded. If you try to use the debugger
- 4 -
Release Notes 4.3.2 PowerMAX OS NightView
to reference the argument later in the routine, the results are
undefined. You can do two things to avoid running into this problem:
o Use the array later in the routine. For example, pass the array
as an argument to another routine. This extends the lifetime of
the original argument.
o Use the debugger to look at the array at the first executable
line of the routine. The value of the original argument probably
still exists at this point.
5.6 Scroll Bars
Some users have had a problem using the scroll bars in the graphical
user interface. When the up-arrow button on a scroll bar is clicked,
the window scrolls the length of the entire window contents, rather
than just one line. This problem is caused by an inappropriate X
resource, which has apparently been copied from one user to another in
much the same way as $HOME/.profile files are often copied:
*XmScrollBar*translations: <Btn1Down>: Select()
You should remove this resource from your $HOME/.Xdefaults or whatever
other means you use for setting X resources. This resource affects
any Motif application, not just NightView.
5.7 Accessing Variables While in Prologue of Subprogram
Because the compilers generate line-number information for code that
comprises the prologue of a subprogram, you may inadvertently set an
eventpoint or stop your program at such a location. The prologue is
the code that the compiler generates to set up the execution
environment for a subprogram; until that code completes execution, the
environment is incomplete. Attempts to access variables while in the
context of the prologue may result in errors from NightView or may
result in erroneous values.
If you suspect such a problem, you can determine whether you are in
the prologue by doing the following:
o Stop the program at the point where the referencing problem
occurs.
o Enter the command info frame.
- 5 -
PowerMAX OS NightView 4.3.2 Release Notes
o If the output from this command says something like "Could not
obtain frame description information", then you are probably
stopped in the prologue.
To try and avoid this problem, do not set an eventpoint on the lines
containing a subprogram heading. If you want to set the eventpoint at
the beginning of the subprogram, use the unit_name (for Ada) or
function_name form of location specifier, rather than a file_name and
line_number. See section 7.1.2, "Location Specifiers".
5.8 Shared Objects
For core files, NightView cannot always find correct stack description
information (tdesc) for shared objects. This problem occurs when the
shared objects are built without position-independent code. This
problem can cause NightView to display the wrong results for any
routine other than the most recently called routine. For example, a
backtrace command may print the wrong information, or an up command
may fail. This is true for any release of NightView, not just 4.3.2.
This is not a problem for running processes, only for core files.
We recommend that you build shared objects with position-independent
code if you plan to debug programs that use them. For C and Fortran,
use the -Zpic option. See cc(1) or f77(1). For Ada, use -sm shared
or -sm both. See "Shared Libraries and Shared-Objects" on page 3-12
of the HAPSE Reference Manual (Pub. No. 0890288-100).
6. Product Description
6.1 New Features in This Release
6.1.1 Auto-Frame_Mode
Auto-frame mode causes NightView to position the current stack frame
to a frame which has associated source code when your process stops
for these reasons:
o New process.
o Stopped by attach.
- 6 -
Release Notes 4.3.2 PowerMAX OS NightView
o About to exit.
o Stopped for a signal.
o Stopped by user.
o Stopped for an exception.
See section 7.4.5.12, "set-auto-frame".
Also, NightView now displays the current stack frame when your process
stops for these reasons, just as it does for a breakpoint or a step
operation.
6.1.2 Unhandled_Ada_Exceptions
The /unhandled_exception option of the handle command allows you to
specify what actions to take when an Ada program raises an exception
but has no handler for it. This allows you to catch these exceptions
before they terminate the process and to examine the program at the
point where the exception was raised. See section 7.8.12, "handle".
6.1.3 Hexadecimal_and_ASCII_Dump
The z option to the x command dumps hexadecimal and ASCII in a side-
by-side format. See section 7.6.4, "x".
6.2 Changes from Previous Releases
6.2.1 Performance_Improvements
NightView 4.3.2 processes symbolic debugging information faster than
earlier releases. Large C++ programs will benefit most.
6.2.2 Child_Processes
4.3.2 fixes a problem that caused child processes to hang in exit if
the child did not exec and the child disposition on the parent was
set-children exec.
- 7 -
PowerMAX OS NightView 4.3.2 Release Notes
6.2.3 Ada_Licenses
4.3.2 fixes a problem with getting an Ada license.
6.2.4 Feedback_from_Commands
4.3.2 always gives feedback from the handle command and from info
commands even if no symbols match the request. See sections 7.8.12,
"handle", 7.12.2.2, "info locals", 7.12.2.3, "info variables",
7.12.2.6, "info functions", 7.12.2.7, "info types", and 7.12.2.10,
"info declaration".
6.2.5 Repeating_List_Command
In earlier releases, repeating a list - command would incorrectly move
forward in the file. This is fixed in 4.3.2. See section 7.5.1.1,
"list".
6.2.6 Listing_C++_Functions
4.3.2 fixes a problem with listing C++ functions from the Source menu.
See section 9.3.13.2, "Debug Source Selection Dialog Box".
6.2.7 List_Function_Dialog_Box
The dialog box for the List Function item of the Source menu now has a
horizontal scroll bar if the function names are too long to fit. See
section 9.3.13.2, "Debug Source Selection Dialog Box".
6.2.8 Global_Objects
A program written in multiple languages may define identical names for
different global objects. 4.3.2 provides a way to refer to these
symbols. See section 3.10.1, "Expression Evaluation".
6.2.9 Signal_Names
The signals SIGADA, SIGGRANT, SIGRETRACT, SIGSAK, and SIGSOUND may now
be referenced by name. See section 7.8.11, "signal" and section
7.8.12, "handle".
- 8 -
Release Notes 4.3.2 PowerMAX OS NightView
6.2.10 Ada_Variant_Records
4.3.2 fixes a bug with displaying variant components of a record
individually.
6.2.11 Directory_Command
The directory command is much faster than before for multiple
directories. See section 7.5.1.2, "directory".
6.2.12 Fully-qualified_Exception_Names
NightView now prints fully-qualified exception names, except that the
debug status area of the Debug Window shows just the simple name to
avoid truncating the status message.
6.2.13 Help_on_Last_Error
4.3.2 fixes a problem with help nodes appearing in the wrong order for
the help command with no arguments and for the On Last Error item in
the Help menu. See section 7.11.1, "help" and section 9.1.2.2 "Help
Menu".
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
- 9 -
PowerMAX OS NightView 4.3.2 Release Notes
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 10 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 3
4. Installation................................................... 3
5. Cautions....................................................... 3
5.1 Ada Tasks, Threads and Lightweight Processes.............. 4
5.2 Ada Support............................................... 4
5.3 Unimplemented Features.................................... 4
5.4 Breakpoint Command Streams................................ 4
5.5 Fortran 77 Arrays......................................... 4
5.6 Scroll Bars............................................... 5
5.7 Accessing Variables While in Prologue of Subprogram....... 5
5.8 Shared Objects............................................ 6
6. Product Description............................................ 6
6.1 New Features in This Release.............................. 6
6.1.1 Auto-Frame Mode................................... 6
6.1.2 Unhandled Ada Exceptions.......................... 7
6.1.3 Hexadecimal and ASCII Dump........................ 7
6.2 Changes from Previous Releases............................ 7
6.2.1 Performance Improvements.......................... 7
6.2.2 Child Processes................................... 7
6.2.3 Ada Licenses...................................... 8
6.2.4 Feedback from Commands............................ 8
6.2.5 Repeating List Command............................ 8
6.2.6 Listing C++ Functions............................. 8
6.2.7 List Function Dialog Box.......................... 8
6.2.8 Global Objects.................................... 8
6.2.9 Signal Names...................................... 8
6.2.10 Ada Variant Records............................... 9
6.2.11 Directory Command................................. 9
6.2.12 Fully-qualified Exception Names................... 9
6.2.13 Help on Last Error................................ 9
7. Direct Software Support........................................ 9
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerMAX OS NightViewTM
Version 4.3.2
Release Notes
0890395-4.3.2P
June 1997
_________________________________________________________________
Trademark Acknowledgments
CX/UX is a trademark of Concurrent Computer
Corporation.
Elan License Manager is a trademark of Elan Computer Group, Inc.
Motif is a trademark of Open Software Foundation,
Inc.
NightView is a trademark of Concurrent Computer
Corporation.
PowerMAX OS is a trademark of Concurrent Computer
Corporation.
PowerPC is a trademark of IBM Corp.
X Window System is a trademark of The Open Group.
return to index
================================================================================
================================================================================
PowerMAX OS NightView*
Version 4.4
Release Notes
Harris Computer Systems Corporation
1. Introduction
NightView is a general-purpose, source-level debugger for Ada, C, C++,
and Fortran. NightView can be used to debug multiple processes on the
local system or on different hosts.
NOTE: NightView is supported on Series 4000 and Series 5000 systems
running CX/UX(TM) and on systems based on the PowerPC(TM) running
PowerMAX OS(TM). This version of the release notes is for PowerMAX
OS.
NightView 4.4 features include:
o Remote debugging. NightView can be used to debug processes on a
remote system.
o Repeated debugging. 4.4 has features that make it easy to debug
the same programs many times with little user interaction.
NOTE: Installation procedures for this product are slightly different
from those for other Concurrent products. Please read the
"Installation" section of these release notes before attempting to
install this product, and carefully follow the installation
instructions.
NOTE: In these release notes, chapter and section references are to
the NightView User's Guide, unless stated otherwise.
__________
* These release notes cover the following products: NightView
- 1 -
PowerMAX OS NightView 4.4 Release Notes
2. Documentation
The following table lists the documentation available with this
release:
___________________________________________
| Manual Name Pub. Number |
|___________________________|______________|
| NightView User's Guide | 0890395-150 |
| NightView Pocket Reference| 0890475-010 |
| NightView Release Notes | 0890395-4.4P|
|___________________________|______________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
3. Prerequisites
Prerequisites for NightView Version 4.4 are as follows:
3.1 Software Prerequisites
o PowerMAX OS release 4.1 or later.
o An X server is required if you are using NightView's graphical
user interface. (The X server may be built into the bitmapped
display device.)
o The X Window System(TM), Version 11R6 with Motif(TM) 2.1.
o Elan License Manager(TM). See the "Installation" section of
these release notes for details.
For more information about configuring your system to support
NightView, see appendix B, "System Resource Requirements", in the
NightView User's Guide.
3.2 Hardware Prerequisites
o Any system based on the PowerPC running PowerMAX OS.
o A bitmapped display device, such as an X terminal, if you are
using NightView's graphical user interface.
- 2 -
Release Notes 4.4 PowerMAX OS NightView
4. Installation
The NightView product is installed as software packages using the
Software Packaging Tools. Please refer to the chapter "Installing
Add-On Software" in the System Administration Manual, Volume 1 (Pub.
No. 0890429), the PowerMAX OS Release Notes (Pub. No. 0890454), and
the pkgadd(1M) command for instructions on software installation.
NightView may be installed in either the root directory or elsewhere.
When you run pkgadd(1M) to install NightView, you are prompted to
enter the name of the directory for installation. If you want to
install in the root directory, just press the RETURN key at the
prompt. Otherwise, enter the name of the directory where you want
NightView installed. If this directory does not exist, the
installation procedures attempt to create it for you.
NOTE: NightView consists of multiple packages. The NightView package
must be installed on systems on which you want to run the NightView
user interface. The Nviewp package must be installed on systems on
which the user programs you want to debug will be running. Most
customers will want both packages on the same system.
If the NightView package is installed before the Nviewp package, you
will get a warning about the Nviewp package not being installed.
NightView must be run with the Elan License Manager. Follow the steps
in the "Obtaining Licenses" section of the Elan License Manager
Release Notes (0891055); the feature alias is NightView. If you are
debugging Ada, then you need an additional license. The Elan feature
alias to debug Ada is NightView_Ada. If you are not already running
the Elan License Manager, if you do not have a copy of the Elan
License Manager Release Notes, or if you need a license key, contact
Concurrent Software Distribution at 1-800-666-5405.
If your site has multiple license servers, and you need to indicate a
server on a particular system, you can set the environment variable
POWERWORKS_ELMHOST to the name of server's system before invoking
NightView. If you used to set the environment variable
HARRIS_ELMHOST, set POWERWORKS_ELMHOST instead. For more information,
see the Elan License Manager Release Notes (0891055).
5. Cautions
- 3 -
PowerMAX OS NightView 4.4 Release Notes
5.1 Ada Tasks, Threads and Lightweight Processes
NightView 4.4 does not yet have direct support for Ada tasks, threads
or lightweight processes. However, the select-context command
provides some support. See section 7.10.4, "select-context".
5.2 Ada Support
Many Ada features are supported, but some are not. See section
3.10.1.1, "Ada Expressions".
5.3 Breakpoint Command Streams
The current implementation of breakpoint command streams does not
include protection against concurrent access of data structures
internal to the debugger. Avoid referencing other processes within
breakpoint command streams. In practice, this is rarely a problem.
5.4 Fortran 77 Arrays
There is currently a problem with Fortran 77 arrays passed as formal
arguments. The compiler generates a temporary variable to optimize
references to the array. This temporary variable is then used in
place of the original array argument. If the original array argument
is not used later in the routine, then the lifetime of the argument is
very short and its value is discarded. If you try to use the debugger
to reference the argument later in the routine, the results are
undefined. You can do two things to avoid running into this problem:
o Use the array later in the routine. For example, pass the array
as an argument to another routine. This extends the lifetime of
the original argument.
o Use the debugger to look at the array at the first executable
line of the routine. The value of the original argument probably
still exists at this point.
5.5 Scroll Bars
Some users have had a problem using the scroll bars in the graphical
user interface. When the up-arrow button on a scroll bar is clicked,
the window scrolls the length of the entire window contents, rather
than just one line. This problem is caused by an inappropriate X
resource, which has apparently been copied from one user to another in
- 4 -
Release Notes 4.4 PowerMAX OS NightView
much the same way as $HOME/.profile files are often copied:
*XmScrollBar*translations: <Btn1Down>: Select()
You should remove this resource from your $HOME/.Xdefaults or whatever
other means you use for setting X resources. This resource affects
any Motif application, not just NightView.
5.6 Accessing Variables While in Prologue of Subprogram
Because the compilers generate line-number information for code that
comprises the prologue of a subprogram, you may inadvertently set an
eventpoint or stop your program at such a location. The prologue is
the code that the compiler generates to set up the execution
environment for a subprogram; until that code completes execution, the
environment is incomplete. Attempts to access variables while in the
context of the prologue may result in errors from NightView or may
result in erroneous values.
If you suspect such a problem, you can determine whether you are in
the prologue by doing the following:
o Stop the program at the point where the referencing problem
occurs.
o Enter the command info frame.
o If the output from this command says something like "Could not
obtain frame description information", then you are probably
stopped in the prologue.
To try and avoid this problem, do not set an eventpoint on the lines
containing a subprogram heading. If you want to set the eventpoint at
the beginning of the subprogram, use the unit_name (for Ada) or
function_name form of location specifier, rather than a file_name and
line_number. See section 7.1.2, "Location Specifiers".
5.7 Shared Objects
For core files, NightView cannot always find correct stack description
information (tdesc) for shared objects. This problem occurs when the
shared objects are built without position-independent code. This
problem can cause NightView to display the wrong results for any
routine other than the most recently called routine. For example, a
backtrace command may print the wrong information, or an up command
may fail. This is true for any release of NightView, not just 4.4.
This is not a problem for running processes, only for core files.
- 5 -
PowerMAX OS NightView 4.4 Release Notes
We recommend that you build shared objects with position-independent
code if you plan to debug programs that use them. For C and Fortran,
use the -Zpic option. See cc(1) or f77(1). For Ada, use -sm shared
or -sm both. See "Shared Libraries and Shared-Objects" on page 3-12
of the HAPSE Reference Manual (Pub. No. 0890288-100).
6. Product Description
6.1 New Features in This Release
6.1.1 Remote_Debugging
NightView allows you to debug processes on a remote system. You can
use remote debugging to control processes on multiple systems from a
single invocation of NightView. You can also use remote debugging to
debug on a system that does not have sufficient resources to run all
of NightView with your application.
Using either the Start Remote Dialogue... item in the NightView menu,
or the login command, you can establish a dialogue on the remote
system. The part of NightView that implements the dialogue uses only
a small part of the system resources because it does not need to read
debug information or control a user interface.
Some systems require precise allocation of resources. NightView lets
you adjust the priority, CPU bias and memory allocation of the
dialogue to minimize the impact of debugging on your application.
See section 3.4.3, "Remote Dialogues".
It is likely that you will need to translate object filenames used on
the remote system so that the local system can find them. See section
7.4.2.4, "translate-object-file".
6.1.2 Repeated_Debugging
Some debugging situations do not require as much interactive control
of the application. NightView 4.4 provides mechanisms to reduce the
amount of user interaction with each process when that is desired.
For information about not stopping for new processes, see section
7.4.4.15, "set-children". For information about not stopping when a
process exits, see section 7.4.4.16, "set-exit". For information
- 6 -
Release Notes 4.4 PowerMAX OS NightView
about not stopping when a process executes a new program, see section
3.6.3, "Restarting a Program".
6.2 Changes from Previous Releases
6.2.1 NightView_Menu
The Create Debug Window... menu item now has the mnemonic D. A new
menu item is added: Start Remote Dialogue.... See section 9.3.1.1,
"Debug NightView Menu".
6.2.2 Default_Qualifier_and_Prompt
The initial default qualifier has changed from local to all, which is
a better default for remote debugging. The initial prompt has changed
from "(%q) " to "(%a) ". %a is a new prompt specifier that prints the
list of dialogues if the default qualifier is all, and otherwise
prints the qualifier (like %q). This causes the normal prompt to
appear the same as in previous releases: (local) . See section
7.4.5.3, "set-qualifier" and section 7.4.5.6, "set-prompt".
6.2.3 Debugger_Environment_Variable
The environment variable NIGHTVIEW_ENV is set to 1 within a dialogue
shell. For remote debugging, it is set to the name of the connecting
system while the shell initializes (e.g., runs .profile). See section
3.4, "Dialogues" and section 7.4.2.1, "login".
6.2.4 apply_on_dialogue
If there is a local dialogue, the debugger automatically performs
(local) apply on dialogue after all initialization files have been
read. See section 7.4.2.7, "apply on dialogue".
6.2.5 Unimplemented_Features
Some unimplemented features and unwritten appendices have been removed
from the NightView User's Guide.
- 7 -
PowerMAX OS NightView 4.4 Release Notes
6.2.6 select-context
NightView now performs auto-frame-mode processing as part of the
select-context command. See section 7.4.5.12, "set-auto-frame", and
section 7.10.4, "select-context".
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 8 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 2
4. Installation................................................... 3
5. Cautions....................................................... 3
5.1 Ada Tasks, Threads and Lightweight Processes.............. 4
5.2 Ada Support............................................... 4
5.3 Breakpoint Command Streams................................ 4
5.4 Fortran 77 Arrays......................................... 4
5.5 Scroll Bars............................................... 4
5.6 Accessing Variables While in Prologue of Subprogram....... 5
5.7 Shared Objects............................................ 5
6. Product Description............................................ 6
6.1 New Features in This Release.............................. 6
6.1.1 Remote Debugging................................... 6
6.1.2 Repeated Debugging................................. 6
6.2 Changes from Previous Releases............................ 7
6.2.1 NightView Menu..................................... 7
6.2.2 Default Qualifier and Prompt....................... 7
6.2.3 Debugger Environment Variable...................... 7
6.2.4 apply on dialogue.................................. 7
6.2.5 Unimplemented Features............................. 7
6.2.6 select-context..................................... 8
7. Direct Software Support........................................ 8
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerMAX OS NightViewTM
Version 4.4
Release Notes
0890395-4.4P
November 1997
_________________________________________________________________
Trademark Acknowledgments
CX/UX is a trademark of Concurrent Computer
Corporation.
Elan License Manager is a trademark of Elan Computer Group, Inc.
Motif is a trademark of Open Software Foundation,
Inc.
NightView is a trademark of Concurrent Computer
Corporation.
PowerMAX OS is a trademark of Concurrent Computer
Corporation.
PowerPC is a trademark of IBM Corp.
X Window System is a trademark of The Open Group.
return to index
================================================================================