Updated 2004/12/06

Sun[tm] Studio 10: Integrated Development Environment (IDE) Readme


Contents

  1. Introduction
  2. About the Sun Studio 10 IDE
  3. New and Changed Features
  4. Supported Source Code Control Software
  5. Components of the Sun Studio 10 Software
  6. Ensuring That the IDE Operates Correctly in a Client/Server Installation
  7. Ensuring That the IDE Can Find the Core Platform
  8. Ensuring That the IDE Can Find the Correct J2SE Technology
  9. Starting the IDE
  10. Software Corrections
  11. Problems and Workarounds
  12. Limitations and Incompatibilities

 

A. Introduction

This document describes the software corrections, known problems, limitations, and incompatibilities of this release.

Product Documentation

 

B. About the Sun Studio 10 IDE

The Sun Studio 10 IDE provides modules for creating, editing, building, debugging, and analyzing the performance of a C, C++, or Fortran application. It includes a set of basic Java[tm] language support modules that can be enabled if needed for JNI (Java[tm] Native Interface) development.

This release of the IDE is available on the following platforms:

 

C. New and Changed Features

This section describes the new and changed features in the IDE.

The following features were added or changed in the Sun Studio 10 IDE:

The following features were added or changed in the Sun Studio 9 IDE:

D. Supported Source Code Control Software

The Sun Studio 10 IDE supports the following source code control software:

E. Components of the Sun Studio Software

The Sun[tm] Studio 10 software consists of two major components:

The IDE, compilers, and tools are installed by default in the /opt/SUNWspro directory on Solaris, but an alternate location can be specified during installation. The IDE and tools are installed in the /opt/sun/sunstudio10 directory on Linux platforms, but an alternate location can be specified during installation.

The core platform is installed by default in the /opt/netbeans/3.5V directory on Solaris platforms, but an alternate location can be specified during installation. The core platform is installed by default in the /opt/sun/netbeans/3.5V directory on Linux platforms, but an alternate location can be specified during installation.

On Solaris platforms, the J2SE 1.4.2_06 technology is installed by default in the /usr/jdk/j2sdk1.4.2_06 directory, but an alternate directory in /usr can be specified during installation. On Linux platforms, the J2SE 1.4.2_06 technology is installed by default in the /usr/java/j2sdk1.4.2_06 directory; but an alternate directory in /usr can be specified during installation.

The correct operation of the IDE depends on the IDE being able to find the core platform, and the core platform being able to find the J2SE technology.

 

F. Ensuring That the IDE Operates Correctly in a Client/Server Installation

The Sun Studio 10 software can be installed on a server. To ensure that the IDE can find the core platform when you start the IDE from a client system, you must mount the directories that contain the IDE and the core platform from the server if they are not installed on the client system.

For convenience, both the IDE and the core platform are installed in the same base directory, so you can use a single mount point on the client system for both.

Note: If the mount point on the client system is the default installation directory, it might hide the installation of other software on the client system. In this case, do not mount the /opt directory. Instead, on Solaris platforms, mount the /opt/SUNWspro directory and /opt/netbeans directory separately. On Linux platforms, mount the /opt/sun/sunstudio10 directory and /opt/sun/netbeans separately.

 

G. Ensuring That the IDE Can Find the Core Platform

The sunstudio command that starts the IDE looks for the core platform in two locations:

If the core platform is not installed or mounted to either of the locations where the sunstudio command looks for it, then each user on a client system must set the environment variable SPRO_NETBEANS_HOME to the location where the core platform is installed or mounted (installation_directory/netbeans/3.5V).

On Solaris platforms, each user of the IDE also must add /installation_directory/SUNWspro/bin to their $PATH in front of the path to any other release of Forte Developer software, Sun ONE Studio software, or Sun Studio software. On Linux platforms, each user of the IDE also must add /installation_directory/sunstudio10/bin to their path in front of the path to any other release of Sun Studio software.

Note: The path /installation_directory/netbeans/3.5V/bin should not be added to the user's $PATH.

 

H. Ensuring That the IDE Can Find the Correct J2SE Technology

The IDE requires the J2SE 1.4.2_06 technology. Each client system must have one of the following:

To determine whether a valid J2SE 1.4.2_06 technology is installed in a standard location on your local system or is in your $PATH, type: 

checkjava

If the checkjava command finds a valid J2SE technology, the output of the command is: 

  Using J2SDK version version from path

If you receive this output, you have the required J2SE available to your system, and the IDE will find it.

If the command does not find a valid J2SE technology, the output of the command is: 

  Could not find valid J2SDK in $PATH or in a standard location

In this case, you have several choices:

 

I. Starting the IDE

The command to start the IDE is sunstudio. For details on this command, see the sunstudio(1) man page. (To display the sunstudio(1) man page, you must have /installation_directory/SUNWspro/man in your $MANPATH on Solaris platforms, and /installation_directory/sunstudio10/man in your $MANPATH on Linux platforms.)

 

J. Software Corrections

This section describes problems that were fixed in the Sun Studio 10 release of the IDE.

  1. The selection was erased after about a second in an XEmacs window
  2. Removing last line closed external editor document connection
  3. GVim didn't respond to IDE if swap file existed
  4. The ~ character did not send a change request to GVim
  5. When using the External Editor module and XEmacs, saving multibyte comments corrupts the saved file.
  6. When using the External Editor module in the Ja locale, breakpoints are shown on the wrong line
  7. The cw command in GVim might corrupt file
  1. The selection was erased after about a second in an XEmacs window (4964962)
  2. Removing last line closed external editor document connection (4985044)

    Removing the last line in a file displayed in GVim stopped the connection between GVim and the IDE. The user was informed that the connection has been lost.

  3. GVim didn't respond to IDE if swap file exists (4801244)

    If you started GVim from the Explorer on a source file that has an existing vim swap file, your GVim showed error E325 about an existing swap file. "Hit ENTER or type command to continue" was displayed at the bottom of your GVim window.

  4. The ~ character did not send a change request to the IDE (4997096)

    Every character changed in a file must send back a message to the IDE telling GVim that the character has been changed. The '~' character did not send this message.

  5. When using the External Editor module and XEmacs, saving multibyte comments corrupted the saved file. (4950716)
  6. When using the External Editor module in the Ja locale, breakpoints was shown on the wrong line (4948883)

    If you set a breakpoint on line 20, it showed on line 21. This may also be a problem in Zh locale.

  7. The cw command in GVim might corrupt file

    Using cw command when editing a file with GVim and then saving the file might result in a corrupted file.

 

K. Problems and Workarounds

This section discusses known software problems and possible workarounds for those problems. For updates or patches, check the updated information at http://developers.sun.com/prodtech/cc/support_index.html.

  1. External Browser Might Not Start or Display Requested Link
  2. The New Breakpoints dialog often is not correctly seeded with the current file and line information when using the external editors GVim or XEmacs
  3. Sometimes get a FileStateInvalidException when starting to debug an executable
  4. Closing and reopening the Output window causes tabs to disappear
  1. External Browser Might Not Start or Display Requested Link

    If you choose the Compiler/Tools Documentation item on the Help menu, or click the link for the Developer Portal in the Welcome screen, the IDE might not successfully start your external browser or use an external browser you are already running to display the documentation index or the Developer Portal.

    Workaround:

    Start your external browser outside the IDE and use the following URLs:

    • For the documentation index page for the Sun Studio 10 for Solaris platforms or Sun Studio 10 for Linux platforms product, which has links to all of the man pages, readmes, and manuals, use installation_directory/SUNWspro/docs
    • For the Developer Portal for Sun Studio, which provides code samples, technical articles, knowledge base items, and documentation, use http://developers.sun.com/prodtech/cc/index.html.

  2. The New Breakpoints dialog often is not correctly seeded with the current file and line information when using the external editors GVim or XEmacs (4981442)

    When the New Breakpoints dialog is displayed, it is supposed to have the Breakpoint Type set to File:Line and the File and Line text fields set according to the cursor in the editor. In many cases, the File and Line fields are blank when the dialog is displayed, so that you must type in the file and line information.

    Workaround:

    There are three ways to display this dialog. If you display it from the Breakpoints view in the Debugger window you almost never see File and l Line information. If you display it from an external editor (GVim or XEmacs) using Shift+Ctrl+F8, File and Line information is correctly set. If you display the dialog from the Debug menu, it depends on where you last typed or clicked in the IDE windows.

  3. Sometimes get a FileStateInvalidException when starting to debug an executable (4960929)

    If you get this exception when starting the debugger, you also get a bad window layout. Exit the IDE and restart.

  4. Closing and reopening the Output window causes tabs to disappear

    If you are running a single debugging session and you close the Output window and subsequently reopen it, the reopened window has only the Output tab.

    Workaround:
    Terminate your debugging session and start a new one, and the Output window will have all of its tabs.

 

L. Limitations and Incompatibilities

This section discusses limitations and incompatibilities with systems or other software. For last-minute information, see the release notes for Solaris platforms at http://developers.sun.com/tools/cc/documentation/ss10_docs/release_notes .html and the release notes for Linux platforms at http://developers.sun.com/tools/cc/documentation/ss10_docs/Linux_release_ notes.html

The Sun Studio 10 IDE has the following limitations:

 

Copyright © 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.