NetBeans™ C/C++ Development Pack 5.5 Release Notes

Welcome to NetBeans C/C++ Development Pack.

NetBeans™ C/C++ Development Pack 5.5 lets you develop C/C++ applications for the Microsoft Windows, Linux, and Solaris Operating Systems with the NetBeans IDE.

NetBeans C/C++ Development Pack 5.5 is compatible with the NetBeans IDE 5.5.

Contents

Note: If you are looking for information about installing the software, see the NetBeans C/C++ Development Pack 5.5 Installation and Setup Instructions.

System Requirements

Supported Operating Systems

NetBeans C/C++ Development Pack 5.5 runs on operating systems that support the Java VM. NetBeans C/C++ Development Pack 5.5 has been tested on the following operating systems:

  • Microsoft Windows XP Professional SP2
  • Red Hat Fedora Core 3
  • Solaris™ 10 Operating System (Solaris OS) (SPARCŪ and x86/x64 Platform Edition)

NetBeans C/C++ Development Pack also runs on the following platforms:

  • Microsoft Windows 2000 Professional SP4
  • Solaris™ 8 OS (SPARC® and x86/x64 Platform Edition) and Solaris™ 9 OS (SPARC® and x86/x64 Platform Edition)
  • Various other Linux distributions

Minimum Hardware Configuration

Note: The NetBeans IDE's minimum screen resolution is 1024x768 pixels.


  • Microsoft Windows operating systems:
    • Processor: 500 MHz Intel Pentium III workstation or equivalent
    • Memory: 512 MB
    • Disk space: 850 MB of free disk space

  • Linux operating system:
    • Processor: 500 MHz Intel Pentium III workstation or equivalent
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space

  • Solaris OS (SPARC):
    • Processor: UltraSPARC II 450 MHz
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space

  • Solaris OS (x86/x64 Platform Edition):
    • Processor: AMD Opteron 100 Series 1.8 GHz
    • Memory: 512 MB
    • Disk space: 450 MB of free disk space

Recommended Hardware Configuration
  • Microsoft Windows operating systems:
    • Processor: 1.4 GHz Intel Pentium III workstation or equivalent
    • Memory: 1 GB
    • Disk space: 1 GB of free disk space

  • Linux operating system:
    • Processor: 1.4 GHz Intel Pentium III or equivalent
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Solaris™ OS (SPARC®):
    • Processor: UltraSPARC IIIi 1 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

  • Solaris™ OS (x86/x64 platform edition):
    • Processor: AMD Opteron 100 Series 1.8 GHz
    • Memory: 1 GB
    • Disk space: 850 MB of free disk space

Required Software

NetBeans C/C++ Development Pack 5.5 runs on the Java 2 Platform Standard Edition Development Kit 5.0 Update 1 or higher (JDK 5.0, version 1.5.0_01 or higher), which consists of the Java Runtime Environment plus developer tools for compiling, debugging, and running applications written in the Java language. Sun Java System Application Server Platform Edition 9 has been tested with JDK 5.0 update 6.

You can download the JDK for your platform from http://java.sun.com/j2se/1.5.0/download.html.


top

Configuration Information

The NetBeans IDE has a default heap size of 128 MB. NetBeans C/C++ Development Pack runs well with this default setting when you are developing small projects with up to 500 source and header files.

When you are developing larger projects, you will need to increase the heap size. If you get an OutOfMemory exception when developing a large project, the heap size is a likely cause.

You can set the heap size for the Java Virtual Machine (JVM)* on which the NetBeans IDE runs in the netbeans.conf file.

To change the heap size:

  1. Copy the netbeans.conf from the etc folder in the NetBeans installation directory into your NetBeans user directory ($HOME/.netbeans/5.5).
  2. In the netbeans.conf file in your user directory, edit the -J-Xmx command line Java startup switch (bolded below) in the netbeans.conf file, and then restart the IDE.
    # command line switches
    netbeans_default_options="-J-Xms32m -J-Xmx128m -J-XX:PermSize=32m 
    -J-XX:MaxPermSize=96m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true"
    

The recommended heap sizes for NetBeans C/C++ Development Pack for medium and large applications are:

  • For developing medium applications (500-2000 source and header files) on a system with 1 GB or more of RAM: 512 MB
  • For developing large applications (more than 2000 source and header files) on a system with 2 GB or more of RAM): 1 GB

Do not increase the heap size to more than 1 GB.

If you are running the Sun JVM, you can also add the garbage collector switches -J-XX:+UseConcMarkSweepGC (concurrent collector) and -J-XX:+UseParNewGC (parallel collector) to the netbeans.conf file. These options allow the garbage collector to run in parallel with the main execution engine. They might not be supported by non-Sun implementations of the JVM.

For more information on NetBeans switch settings, see the Configuring the IDE section of Using NetBeans IDE 5.5

For more information on NetBeans performance tuning, see Tuning JVM Switches for Performance.

* Note: The terms "Java Virtual Machine" and "JVM" mean a Virtual Machine for the Java(TM) platform.

/se/tpubs/Work/

top


Known Issues

This NetBeans C/C++ Development Pack 5.5 release lets you explore and evaluate new functionality in the IDE. We encourage you to get involved and give us feedback by logging any issues you encounter in the Issue Tracking system at https://netbeans.org/community/issues.html.

The unresolved issues for this release are as follows:

  • Issue #75120: Terminate Process is failing

    Description: Attempting to terminate a running process from the Runtime tab does not always terminate the process. The Runtime tab lists the process as terminated, but might not really be terminated.

    Workaround: Before terminating a process in the IDE, check the process ID by using the ps command on UNIX or the Task Manager on Windows. After terminating the process in the IDE, check that the process was really terminated. If not, use the kill command on UNIX systems or End Process in the Task Manager on Windows.

  • Issue #89872: "Parser Settings" for Sun Compiler Collection are incorrect

    Description: Include directives for <cstdlib>, <cstring> and some other files are underlined as erroneous when the Sun Compiler Collection is used.

    Workaround: Add the include search paths manually:

    1. Select Tools > Options.
    2. In the Options dialog box, select the C/C++ node and click Parser Settings.
    3. Select the Sun Compiler Collection in the drop-down list, and click the Sun C++ Compiler tab.
    4. Add the correct paths using the Add button.

  • Issue #90026: Quick Navigator works incorrectly after source file was renamed

    Description: When you rename a file, the Quick Navigator (a drop-down box in the editor toolbar that displays the outline for the current file) does not work properly.

    Workaround: Close the file and then reopen it.

  • Issue #89880: Project is not reparsed when Compiler Collection is switched

    Description: If you switch compiler collections for a project, the project is not reparsed. After the switch, code completion and hyperlinks might not work properly for the project.

    Workaround: Close the project and open it again.

  • Issue #89876: gdb-lite is broken for applications compiled by Sun compilers collection

    Description: The debugger does not always work properly for projects compiled with the Sun Compiler Collection.

    Workaround: The Sun Studio Compiler Collection has had little official testing with the gdb debugger. An unofficial developer study produced mixed results in testing several gdb versions with the Sun Studio compilers on Linux and the Solaris OS. You can see these results at http://cnd.netbeans.org/gdb-sscc.html.

  • Issue #79023: Class View should reduce time spent in updating tree for large projects.

    Description: For large projects and especially for projects with a "plain" structure (projects that are not well structured using namespaces), having the Class View open while the project is being parsed might slow down parsing noticeably.

    Workaround: If you think parsing your project is taking too long, close the Class View and reopen it after the project is completely parsed.

  • Issue #76173: No automatic flush of output before input

    Description: When running a C or C++ program, the OS flushes stdout before reading from stdin. This flushing does not occur if you run the program in the Output window.

    Workaround: In the Running category of the project properties, set the Console Type to External Terminal or Default.

  • Issue #89514: Input field in Output panel is misleading when external terminal is used

    Description: When you run a program in an external terminal, the Output window in the IDE has an Input field. Text typed into this field is ignored and does not go to the running program. The program reads all input from the external terminal.

    Workaround: Ignore the Input field. Use the external terminal for all programs receiving terminal input.

  • Issue #89962: $PATH is corrupted for projects with dependent library projects

    Description: The IDE incorrectly overrides the PATH variable for a project on Windows that depends on either C/C++ Static Library or C/C++ Dynamic Library projects. The program may not run.

    Workaround: Start NetBeans from a Cygwin terminal instead of from the Desktop or Start menu.

  • Issue #89718: Confusing output for running process. Process is not shown in Runtime tab.

    Description: The message Run successful. Exit value 0. appears immediately after the program starts.

    Workaround: If you need to check your program's exit value and are not doing terminal input, set the Console Type in the Running node of the project properties to Output Window (Input Only). If you don't need to check your program's exit code or if you are doing terminal input, you don't need to change anything.

    There is no workaround if you are doing terminal input and you need to check your program's exit code. In this case, you might want to run your program outside the IDE.

  • Issue #89966: Gnome terminal ignores environment variables

    Description: If you run a program in the Gnome terminal, environment variables aren't passed properly to the program.

    Workaround: In the Running node of the project properties, set Terminal Type to XTerm or set Console Type to Output Window (Input Only).

  • Issue #89334: wrong return code printed when using external terminal window

    Description: The Output window should display the return code of the application and print something like Failed. Return code = 5 when the application fails (returns something other than 0). But it always displays Succeeded. Return code = 0.

    Workaround: If you need to see your program's exit value, set Console Type to Output Window (Input Only) in the Running node of the project properties. If you don't care about the exit value, no change is necessary.

  • Issue #90117: "Terminal Type" should be disabled if "Output Window (Input Only)" is selected

    Description: The IDE ignores the setting of Terminal Type if Console Type is set to Output Window (Input only).

    Workaround: Ignore the Terminal Type option.

  • Issue #89343: Pause doesn't work on Windows when program waits user input

    Description: Clicking Pause while a program is waiting for input does not stop the program. Pause works only after you supply the input.

    Workaround: No workaround.

  • Issue #90120: "pause" (on Windows) does not work on a corner case

    Description: Besides 89343, there are several other cases when Pause does not work on Windows. One case is in very tight loops.

    Workaround: No workaround.

  • Issue #90222: Breakpoints don't take immediate effect while running

    Description: If a breakpoint is set on a running process, the breakpoint is not passed to gdb until the next time the process is stopped.

    Workaround: Pause the process, set the breakpoint, and continue.

  • Issue #90235: Console type "Output Window (input only)" should be "output only"

    Description: The NetBeans Output window does not handle input well. NetBeans C/C++ Development Pack provides a Console Type project property that lets you decide whether your program is run with I/O going to the Output window or to an external terminal (which is the default). The label for sending program I/O to the Output window says "input only". It should read "output only".

    Workaround: In the Running node of the project properties, use the default Console Type of External Terminal.

Documentation

Documentation for the NetBeans C/C++ Development Pack 5.5 release is provided in the form of web-based guides and the IDE's help system. You can use the following documents to get started:

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2016, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo