Conference turris::decladebug

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  January 23, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    SUBJECT:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-28, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.0 and V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    This release of the Ladebug debugger has been submitted for BL3 of
    Digital UNIX V4.0B.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with Window Interface for the Digital UNIX platform.  Key features of 
    Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  NEW FEATURES AND KNOWN LIMITATIONS

    Many bugs have been fixed in this release of the debugger.

    Significant performance improvements have been made to the Ladebug
    debugger.  

    The release of the Window Interface in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    The debugger software has been modified to allow localization to other
    language locales.  This "internationalized" version is available in a
    kit on the Base Systems CD-ROM and may be installed only on Digital UNIX
    V4.0A.  To install this kit, you must install the "IOSLDB" subsets that
    appear with the rest of the Worldwide Support subsets on the Base Systems
    CD-ROM.

    The Window Interface of the Ladebug debugger has been integrated into
    the Common Desktop Environment.

    The release of the Window Interface in these kits works only with the
    Ladebug debugger that is included in these kits.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.0 or V3.2 systems.  Please refer to the release
    notes for full details.


1.1  C++ Run-Time Support Library

1.1.1  DEC OSF/1 V3.0

    In order to use this version of Ladebug on DEC OSF/1 V3.0, a special
    release of the C++ Run-Time library is required.  You may obtain a kit
    of this library via anonymous ftp:

	ftp://labrea.zko.dec.com/pub/cxxl/CXXSHRDA305-OSF1-V3.0.tar


1.1.2  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the "DEC C++ Class Library, Run-Time Support" subset
    from the "DEC C++ V5.4-6" kit.  The subset name is CXXSHRDA307.
    See TURRIS::C_PLUS_PLUS Note 3079.5 for the announcement of this kit.

    You can retrieve the DEC C++ V5.4-6 kit from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or via anonymous ftp directly:

	ftp://labrea.zko.dec.com/pub/C++/cxx540/unix/CXX540V06.tar


1.1.3  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.



2  KIT LOCATION

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-28 for DEC OSF/1 V4.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB428/LDB428-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB428/LDB428-v4.0.tar

    Ladebug Debugger Version 4.0-28 for DEC OSF/1 V3.2 and Digital Unix V3.2C:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB428/LDB428-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB428/LDB428-v3.2.tar

    Ladebug Debugger Version 4.0-28 for DEC OSF/1 V3.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB428/LDB428-v3.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB428/LDB428-v3.0.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB428/ladebug-relnotes.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB428/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB428/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB428/cover-letter.txt



3  KIT INSTALLATION

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  DOCUMENTATION

    Documentation (in various formats) can be found at:

WWW:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

FTP:
    ftp://asaab.zko.dec.com/pub/Ladebug/doc/ladebug_manual.v4.0.ps
    ftp://asaab.zko.dec.com/pub/Ladebug/doc/ladebug_manual.v4.0.bookreader.tar

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  PROBLEM REPORTS (QARs) AND NOTESFILES

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the Window Interface, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only

I have removed the kit from the directory temporarily due to
the problem found in dxladebug callstack button.   Sign :-(

Sorry about this.

Wanfang Murray

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  February 7, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    SUBJECT:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-30, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.0 and V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with Window Interface for the Digital UNIX platform.  Key features of 
    Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  NEW FEATURES AND KNOWN LIMITATIONS

1.1  What's New at Version 4.0-30

    See the release notes for full details about new features and bug
    fixes.

    C++ dynamic type support has been added.  This support is off by
    default at 4.0-30, but will be turned on by default in a future
    release.

    The performance of source scrolling in the Window Interface has been
    greatly improved.

    Default aliases have been added in an effort to better support dbx
    commands.

    Improvements have been made to support Fortran programs.


1.2  Internationalization

    Differences in internationalization support in the debugger will
    affect subset installation on different "letter" releases of Digital
    UNIX V4.0 (such as V4.0B, V4.0C, etc.).  See the release notes for
    full details.


1.3  DEC FUSE

    The release of the Window Interface in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.0 or V3.2 systems.  Please refer to the release
    notes for full details.


1.4  C++ Run-Time Support Library

1.4.1  DEC OSF/1 V3.0

    In order to use this version of Ladebug on DEC OSF/1 V3.0, a special
    release of the C++ Run-Time library is required.  You may obtain a kit
    of this library via anonymous ftp:

	ftp://labrea.zko.dec.com/pub/cxxl/CXXSHRDA305-OSF1-V3.0.tar


1.4.2  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the "DEC C++ Class Library, Run-Time Support" subset
    from the "DEC C++ V5.4-6" kit.  The subset name is CXXSHRDA307.
    See TURRIS::C_PLUS_PLUS Note 3079.5 for the announcement of this kit.

    You can retrieve the DEC C++ V5.4-6 kit from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or via anonymous ftp directly:

	ftp://labrea.zko.dec.com/pub/C++/cxx540/unix/CXX540V06.tar


1.4.3  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.


1.5  General

    The Window Interface of the Ladebug debugger has been integrated into
    the Common Desktop Environment.

    The release of the Window Interface in these kits works only with the
    Ladebug debugger that is included in these kits.



2  KIT LOCATION

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-30 for DEC OSF/1 V4.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB430/LDB430-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB430/LDB430-v4.0.tar

    Ladebug Debugger Version 4.0-30 for DEC OSF/1 V3.2 and Digital Unix V3.2C:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB430/LDB430-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB430/LDB430-v3.2.tar

    Ladebug Debugger Version 4.0-30 for DEC OSF/1 V3.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB430/LDB430-v3.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB430/LDB430-v3.0.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/doc/release-notes/4.0-30.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB430/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB430/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB430/cover-letter.txt



3  KIT INSTALLATION

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  DOCUMENTATION

    Documentation (in various formats) can be found at:

WWW, FTP: see:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  PROBLEM REPORTS (QARs) AND NOTESFILES

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the Window Interface, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  April 7, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    Subject:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-35, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.0 and V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with graphical user interface (GUI) for the Digital UNIX platform.  
    Key features of Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  New features and known limitations

1.1  What's new at Version 4.0-35

    See the release notes for full details about new features and bug
    fixes.

    Support for the C++ V5.6 compiler has been added.

    The ability to modify register values in the GUI Register View has
    been disabled.


1.2  Internationalization

    Differences in internationalization support in the debugger will
    affect subset installation on different "letter" releases of Digital
    UNIX V4.0 (such as V4.0B, V4.0C, etc.).  See the release notes for
    full details.


1.3  DEC FUSE

    The release of the GUI in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.0 or V3.2 systems.  Please refer to the release
    notes for full details.


1.4  C++ Run-Time support library

1.4.1  DEC OSF/1 V3.0

    In order to use this version of Ladebug on DEC OSF/1 V3.0, a special
    release of the C++ Run-Time library is required.  You may obtain a kit
    of this library via anonymous ftp:

	ftp://labrea.zko.dec.com/pub/cxxl/CXXSHRDA305-OSF1-V3.0.tar


1.4.2  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the "DEC C++ Class Library, Run-Time Support" subset
    from the "DEC C++ V5.4-6" kit.  The subset name is CXXSHRDA307.
    See TURRIS::C_PLUS_PLUS Note 3079.5 for the announcement of this kit.

    You can retrieve the DEC C++ V5.4-6 kit from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or via anonymous ftp directly:

	ftp://labrea.zko.dec.com/pub/C++/cxx540/unix/CXX540V06.tar


1.4.3  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.


1.5  General

    The Ladebug debugger GUI has been integrated into the Common Desktop
    Environment.

    The release of the GUI in these kits works only with the Ladebug
    debugger that is included in these kits.



2  Kit location

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-35 for DEC OSF/1 V4.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB435/LDB435-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB435/LDB435-v4.0.tar

    Ladebug Debugger Version 4.0-35 for DEC OSF/1 V3.2 and Digital Unix V3.2C:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB435/LDB435-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB435/LDB435-v3.2.tar

    Ladebug Debugger Version 4.0-35 for DEC OSF/1 V3.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB435/LDB435-v3.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB435/LDB435-v3.0.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/doc/release-notes/4.0-35.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB435/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB435/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB435/cover-letter.txt



3  Kit installation

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  Documentation

    Documentation (in various formats) can be found at:

WWW, FTP: see:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  Problem reports (QARs) and notesfiles

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the GUI, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  April 30, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    Subject:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-36, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.0 and V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with graphical user interface (GUI) for the Digital UNIX platform.  
    Key features of Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  New features and known limitations

1.1  What's new at Version 4.0-36

    See the release notes for full details about new features and bug
    fixes.

    o  Enhanced symbol lookup

    o  Thread Local Storage

    o  Enhanced watchpoint information


1.2  Internationalization

    Differences in internationalization support in the debugger will
    affect subset installation on different "letter" releases of Digital
    UNIX V4.0 (such as V4.0B, V4.0C, etc.).  See the release notes for
    full details.


1.3  DEC FUSE

    The release of the GUI in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.0 or V3.2 systems.  Please refer to the release
    notes for full details.


1.4  C++ Run-Time support library

1.4.1  DEC OSF/1 V3.0

    In order to use this version of Ladebug on DEC OSF/1 V3.0, a special
    release of the C++ Run-Time library is required.  You may obtain a kit
    of this library via anonymous ftp:

	ftp://labrea.zko.dec.com/pub/cxxl/CXXSHRDA305-OSF1-V3.0.tar


1.4.2  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the 3.0-7 version of the "DEC C++ Class Library, 
    Run-Time Support" library from a DEC C++ kit.  The subset name is
    CXXSHRDA307.  See the TURRIS::C_PLUS_PLUS Notes Conference for
    announcements of their kits.

    You can retrieve DEC C++ kits from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or by using anonymous ftp directly, beginning at this directory:

	ftp://labrea.zko.dec.com/pub/C++/


1.4.3  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.


1.5  General

    The Ladebug debugger GUI has been integrated into the Common Desktop
    Environment.

    The release of the GUI in these kits works only with the Ladebug
    debugger that is included in these kits.



2  Kit location

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-36 for DEC OSF/1 V4.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB436/LDB436-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB436/LDB436-v4.0.tar

    Ladebug Debugger Version 4.0-36 for DEC OSF/1 V3.2 and Digital Unix V3.2C:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB436/LDB436-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB436/LDB436-v3.2.tar

    Ladebug Debugger Version 4.0-36 for DEC OSF/1 V3.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB436/LDB436-v3.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB436/LDB436-v3.0.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/doc/release-notes/4.0-36.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB436/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB436/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB436/cover-letter.txt



3  Kit installation

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  Documentation

    Documentation (in various formats) can be found at:

WWW, FTP: see:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  Problem reports (QARs) and notesfiles

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the GUI, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only

One of our important internal sites is reporting major problems with the -BL36
kit attempting to debug 

	ANYTHING that dealt with pthreads.
        Core dumps.
	Attaching to running processes.

We will be investigating immediately.

If these scenarios apply to you, then DON'T pick up this kit.
                                      
/Bevin

We have identified two underlying problems

    	Can't debug a core file from a threads program

    	    We hope to have this fixed this afternoon

    	    Our test system had quite a few core tests, but no
    	    threads core tests, hence this regression from BL35 to BL36
    	    went unnoticed.

    	If you either use the -pid option, or the attach command,
    	then there is a timing window during which typing ^C
    	fails to stop the attached-to process and leads to a very
    	misleading message about being unable to attach

    	    You can work around this by waiting a few seconds before
    	    typing ^C

    	    We *may* be able to get this fixed this afternoon.

We will be cutting a new kit in the morning.

/Bevin

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  May 6, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    Subject:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-37, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.0 and V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with graphical user interface (GUI) for the Digital UNIX platform.  
    Key features of Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  New features and known limitations

1.1  What's new at Version 4.0-37

    See the release notes for full details about new features and bug
    fixes.

    o  Problem fixed in debugging DECthreads programs with core files


1.2  Internationalization

    Differences in internationalization support in the debugger will
    affect subset installation on different "letter" releases of Digital
    UNIX V4.0 (such as V4.0B, V4.0C, etc.).  See the release notes for
    full details.


1.3  DEC FUSE

    The release of the GUI in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.0 or V3.2 systems.  Please refer to the release
    notes for full details.


1.4  C++ Run-Time support library

1.4.1  DEC OSF/1 V3.0

    In order to use this version of Ladebug on DEC OSF/1 V3.0, a special
    release of the C++ Run-Time library is required.  You may obtain a kit
    of this library via anonymous ftp:

	ftp://labrea.zko.dec.com/pub/cxxl/CXXSHRDA305-OSF1-V3.0.tar


1.4.2  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the 3.0-7 version of the "DEC C++ Class Library, 
    Run-Time Support" library from a DEC C++ kit.  The subset name is
    CXXSHRDA307.  See the TURRIS::C_PLUS_PLUS Notes Conference for
    announcements of their kits.

    You can retrieve DEC C++ kits from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or by using anonymous ftp directly, beginning at this directory:

	ftp://labrea.zko.dec.com/pub/C++/


1.4.3  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.


1.5  General

    The Ladebug debugger GUI has been integrated into the Common Desktop
    Environment.

    The release of the GUI in these kits works only with the Ladebug
    debugger that is included in these kits.



2  Kit location

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-37 for DEC OSF/1 V4.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB437/LDB437-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB437/LDB437-v4.0.tar

    Ladebug Debugger Version 4.0-37 for DEC OSF/1 V3.2 and Digital Unix V3.2C:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB437/LDB437-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB437/LDB437-v3.2.tar

    Ladebug Debugger Version 4.0-37 for DEC OSF/1 V3.0:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB437/LDB437-v3.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB437/LDB437-v3.0.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/doc/release-notes/4.0-37.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB437/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB437/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB437/cover-letter.txt



3  Kit installation

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  Documentation

    Documentation (in various formats) can be found at:

WWW, FTP: see:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  Problem reports (QARs) and notesfiles

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the GUI, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only

4.0-37 replaces the 4.0-36 release of 30-April-1997.
Those kits are no longer available.

-Chris

		      Digital Internal Use Only

 +---------------------------+
 |   |   |   |   |   |   |   |
 | d | i | g | i | t | a | l |   I n t e r o f f i c e  M e m o r a n d u m
 |   |   |   |   |   |   |   |
 +---------------------------+
                                         Date:  May 30, 1997
                                         From:  Ladebug team
                                         Dept:  Debug Technologies Group


    Subject:  Digital Ladebug for Digital UNIX Systems


    Digital Ladebug for Digital UNIX Systems, Version 4.0-38, is now 
    available in network kits.  

    These kits are for Digital Internal Use Only and should not be given
    to external customers.  Send any questions concerning this policy 
    to the Project Leader at: [email protected]

    Network kits are available for DEC OSF/1 Systems V3.2,
    and for Digital UNIX (formerly DEC OSF/1) V3.2C, D, etc. and V4.0.

    Digital Ladebug for Digital UNIX Systems is a fully symbolic debugger
    with graphical user interface (GUI) for the Digital UNIX platform.  
    Key features of Ladebug allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide I18N support for local language characters

    Ladebug supports the debugging of programs written in C, C++, Fortran, 
    Fortran 90, Ada and COBOL.  Ladebug features expression evaluation using
    the syntax of the source programming language.

    For full information about the Ladebug debugger, please refer to the
    following manual (see the "DOCUMENTATION" section below for how to
    retrieve this manual):

	Digital UNIX: Ladebug Debugger Manual



1  New features and known limitations

1.1  What's new at Version 4.0-38

    See the release notes for full details about new features and bug
    fixes.

    o  Search Source File dialog box

    o  REAL*16 and long double support

    o  Improved Fortran support

    o  Kits are no longer available for DEC OSF/1 V3.0.


1.2  Internationalization

    Differences in internationalization support in the debugger will
    affect subset installation on different "letter" releases of Digital
    UNIX V4.0 (such as V4.0B, V4.0C, etc.).  See the release notes for
    full details.


1.3  DEC FUSE

    The release of the GUI in these kits works with DEC FUSE
    Version V3.1 only.  Please refer to the release notes for details.

    Installation problems will occur if DEC FUSE is or will be installed
    on your DEC OSF/1 V3.2 systems.  Please refer to the release
    notes for full details.


1.4  C++ Run-Time support library

1.4.1  DEC OSF/1 V3.2 and Digital UNIX V3.2

    You must install the 3.0-7 version of the "DEC C++ Class Library, 
    Run-Time Support" library from a DEC C++ kit.  The subset name is
    CXXSHRDA307.  See the TURRIS::C_PLUS_PLUS Notes Conference for
    announcements of their kits.

    You can retrieve DEC C++ kits from the DEC C/C++ kits web page:

	http://www.zk3.dec.com/decc/decc-kitinfo.html

    Or by using anonymous ftp directly, beginning at this directory:

	ftp://labrea.zko.dec.com/pub/C++/


1.4.2  Digital UNIX V4.0

    No special action is necessary when installing this version of Ladebug
    on Digital UNIX V4.0.


1.5  General

    The Ladebug debugger GUI has been integrated into the Common Desktop
    Environment.

    The release of the GUI in these kits works only with the Ladebug
    debugger that is included in these kits.



2  Kit location

    You may retrieve the kits from the Ladebug Kit Information web page at:

	http://asaab.zko.dec.com/Ladebug/kitinfo/kitinfo-index.html

    Here, for your convenience, are the locations of the kits and related
    documentation.  The lines beginning with "ftp:" are Web URLs that you
    may copy directly into the Open box of your Web viewer.  The "DECNET:"
    lines show the pathname that you would copy in a UNIX "dcp" command.

    Ladebug Debugger Version 4.0-38 for DEC OSF/1 V4.0 and variants:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB438/LDB438-v4.0.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB438/LDB438-v4.0.tar

    Ladebug Debugger Version 4.0-38 for DEC OSF/1 V3.2 and Digital Unix V3.2:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB438/LDB438-v3.2.tar
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB438/LDB438-v3.2.tar

    Ladebug Debugger release notes:
	ftp://asaab.zko.dec.com/pub/Ladebug/doc/release-notes/4.0-38.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB438/ladebug-relnotes.txt

    this cover letter:
	ftp://asaab.zko.dec.com/pub/Ladebug/kits/alpha/LDB438/cover-letter.txt
        DECNET: sdesv1::/usr/proj/debug/public/kits/alpha/LDB438/cover-letter.txt



3  Kit installation

    To install your kit you must be logged in as root, and you must complete the
    following steps.

        1. Copy the appropriate tar set for the version of the Operating
           System on which you will install the kit.

        2. Unpack the tar set with this command:

                # tar -xvf <tar-file-name>

           You may delete the tar set at this time. (Once you have completed the
           installation, you may delete all of the files produced by this step.)


        3. Deinstall previous versions of the subsets on this kit (this step is
           not necessary if this is your first kit).  To see what subsets are
           currently installed, issue the following command:

                # setld -i | grep LDB

            and note which subsets are marked as "installed".  Then issue a
            setld "delete" command to remove those subsets.  For example:

                # setld -d LDBBASE3016 LDBGUI3016


        4. Finally, to install the current kit, execute the command:

                # setld -l <name-of-the-scratch-directory>



4  Documentation

    Documentation (in various formats) can be found at:

WWW, FTP: see:
    http://asaab.zko.dec.com/Ladebug/docinfo/docinfo-index.html

DECNET:
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.ps
    sdesv1::/usr/proj/debug/public/kits/doc/ladebug_manual.v4.0.bookreader.tar




5  Problem reports (QARs) and notesfiles

    Use standard network access to the QAR system (GORGE) for interactively
    entering and reading bug reports.  The username is QAR_INTERNAL.
    The QAR database is OSF_QAR and the component name is LADBX.

    If you have questions about the Ladebug debugger, please consult the
    TURRIS::DECLADEBUG Notes Conference.

    When you submit a QAR or report a problem in the Notes Conference,
    it will be most helpful to include the following information:

	- The Ladebug version number as reported in the "Welcome" banner.
	- If you are running the GUI, the results of issuing
	  "$ show version" in the command window (include the dollar sign).
	- The source code of a sample program or an executable binary.
	- The system configuration.
	- The exact steps used to reproduce the problem.
	- If the executable program is compiled with a compiler that supports
	  the "-P" option, please include a .i or .ixx file.

			Digital Internal Use Only