Contents

1. Introduction
2. About Sun Studio 11 dbx
3. New and Changed Features
4. Software Corrections
5. Problems and Workarounds
6. Limitations and Incompatibilities
7. Documentation Errata

 

---

A. Introduction

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

Product Documentation

• Release Notes for Solaris Platforms: Available on the Sun Developer Network (SDN) Sun Studio portal at http://developers.sun.com/sunstudio/documentation/ss11/release_notes.html. Information in the release notes updates and extends information in all readme files.
• Release Notes for Linux Platforms: Available on the SDN Sun Studio portal at http://developers.sun.com/sunstudio/documentation/ss11/Linux_release_notes.html . Information in the release notes updates and extends information in all readme files.
• Sun Studio Documentation: Product man pages, HTML versions of readmes, and manuals can be accessed from /installation_directory/docs/index.html. The default installation directory on Solaris platforms is /opt/SUNWspro. The default installation directory on Linux platforms is /opt/sun/sunstudio11.
• IDE Documentation: Online help for all components of the Sun Studio IDE can be accessed from the Help menu and Help buttons in the IDE.
• Developer Resources Portal: For technical articles, code samples, documentation, and a knowledge base, see the SDN Sun Studio portal at http://developers.sun.com/prodtech/cc.

 

---

B. About Sun Studio 11 dbx

dbx is an interactive, source-level, command-line debugging tool. You can use it to run a program in a controlled manner and to inspect the state of a stopped program. dbx gives you complete control of the dynamic execution of a program, including the collection of performance data. This release of dbx is available on the following platforms:

• Solaris[tm] Operating System (Solaris OS), versions 8, 9, and 10
• Linux operating system:
  • SuSE Linux Enterprise Server 9 (en locale only, not supported in ja and zh locales)
  • Red Hat Enterprise Linux 4

 

---

C. New and Changed Features

This section describes the new and changed features for dbx.

The following features were added or changed in Sun Studio 11 dbx.

• Support for the AMD64 architecture on the Linux operating system
• Support for the Sun Studio C compiler generating DWARF symbolic debugging information
• New thr_create and thr_exit events
• New step_abflow environment variable
• Revised syntax for the intercept and unintercept commands
• Support for Java[tm] 2 Platform, Standard Edition v 5.0 (J2SE) technology with the exception of some new Java language constructs

A few features of dbx are not available for programs compiled with the gcc or g++ compilers, or for programs running on Linux platforms. For more information, see Limitations and Incompatibilities.

 

---

D. Software Corrections

This section describes problems that were fixed in the Sun Studio 11 release of dbx.

No new information is available at this time.

 

---

E. Problems and Workarounds

This section discusses known software problems and possible workarounds for those problems.

1. Data Collection Problems When dbx is Attached to a Process
2. dbx does not check for an RUI coming from a copy constructor
3. dbx might crash while debugging Java code
4. dbx crashes on re-debugging of Java code
5. dbx cannot debug 32-bit multithreaded applications on Linux platforms
6. dbx throws an exception when debugging application on different J2SE than it was built on

1. Data Collection Problems When dbx is Attached to a Process

   If you attach dbx to a running process without preloading the collector library, libcollector.so, a number of errors can occur.

   • You cannot collect any tracing data: synchronization wait tracing, heap tracing, or MPI tracing. Tracing data is collected by interposing on various libraries, and if libcollector.so is not preloaded, the interposition cannot be done.
   • If the program installs a signal handler after dbx is attached to the process, and the signal handler does not pass on the SIGPROF and SIGEMT signals, profiling data and sampling data is lost.
   • If the program uses the asynchronous I/O library, libaio.so, clock-based profiling data and sampling data is lost, because libaio.so uses SIGPROF for asynchronous cancel operations. (4397578)
   • If the program uses the hardware counter library, libcpc.so, hardware-counter overflow profiling experiments are corrupted because both the collector and the program are using the library. If the hardware counter library is loaded after dbx is attached to the process, the hardware-counter experiment can succeed provided references to the libcpclibrary functions are resolved by a general search rather than a search in libcpc.so.
   • If the program calls setitimer(2), clock-based profiling experiments can be corrupted because both the collector and the program are using the timer.

2. dbx does not check for an RUI coming from a copy constructor

Runtime checking can erroneously report RUI (read from uninitialized memory) for inlined C++ copy constructors.

3. dbx might crash while debugging Java code (4893079)

If you issue a cd command from within the dbx shell, or set the CLASSPATH environment variable or the CLASSPATHX environment variable, dbx might subsequently crash with a segmentation fault..

Workarounds:

• Do not do any of the above.
• Delete all watches (displays) before doing any of the above.

4. dbx crashes on re-debugging of Java code (4801883)

Issuing two debug commands in a row on Java code might cause dbx to crash.

5. dbx cannot debug 32-bit multithreaded applications on Linux platforms

dbx cannot debug 32-bit multithreaded applications on SuSE Linux Enterprise Server 9 and Sun[tm] Java Desktop System, Release 3.

6. dbx throws an exception when debugging application on different J2SE than it was built on

dbx throws an exception when you debug an application under a different release of the J2SE technology than the version of the J2SE technology under which you built the application.

Check the support page on the SDN Sun Studio portal, http://developers.sun.com/sunstudio/support/ for the latest information.

 

---

F. 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/sunstudio/documentation/ss11/release_notes.html and the release notes for Linux platforms at http://developers.sun.com/tools/prodtech/documentation/ss11/Linux_release_notes.html

Sun Studio 11dbx has the following limitations:

• The following features of dbx are not available on the Linux OS on x86 based systems:
  • Fix and continue
  • Performance data collection
  • Runtime checking
  • Breakpoints on the following events:
    • fault
    • lastrites
    • lwp_exit
    • sysin
    • sysout
    • sync
    • throw



• The following features of dbx are not available on the Linux OS on x64 based systems:
  • Java debugging
  • Debugging 32-bit programs, unless you start dbx with the -x exec32 option.



• dbx cannot follow forked processes on Linux platforms or change to a new program when exec() is called.
  
  
• The pipe operator in the Korn shell is limited on Linux platforms. Any dbx command that needs to access the target process does not work as part of a pipeline. For example, the following command is likely to cause dbx to hang:

  where | head -1
  

  Workarounds:

  • Type Ctrl-C to display a new dbx prompt.
  • dbx caches a lot of information, so for the above example, the following sequence of commands works:

    where
    where | head -1
    

• The following problems may occur when debugging programs on Linux platforms:

  • If a program uses clone() to implement its own style of threads, then thread support in dbx does not identify threads correctly.

    Workaround:
    Use libthread.so rather than clone().

  • The threads library in the Linux OS uses SIGSTOP signals as part of its internal mechanism. Normally dbx hides these signals from you, and allows you to monitor genuine SIGSTOP signals from other sources. Occasionally the Linux OS uses SIGSTOP in an unexpected way and dbx interprets a system-generated SIGSTOP as a user-generated SIGSTOP.

    Workaround:
    Use the ignore command to tell dbx not to catch SIGSTOP signals.

  • Sometimes a thread exits, but the Linux OS does not report the exit to dbx. This happens less often when using the new threads library (NPTL).

    When a thread exits and the exit is not reported, dbx waits for an event that will never happen and does not display a new prompt. This situation is most likely to occur after you have given a cont command in dbx, but it can also happen after the step up command, step command, next command, and other commands.

    Workarounds:

    • Sometimes typing Ctrl-C causes dbx to stop waiting and display a new prompt.
    • If Ctrl-C does not work, exit dbx and restart it.

  
  
  
• Run-time type information for C++ expressions is not available for programs compiled with the g++ compiler.



• The memory access checking feature of runtime checking is not available on the Solaris OS on x86 based systems or x64 based systems, or on the Linux OS on x86 based systems or x64 based systems.



• It is not possible to attach to a running process from your .dbxrc file. A .dbxrc file should not contain commands that execute your code. However, you can put such commands in a file, and then use the dbx source command to execute the commands in that file.



• dbx incorrectly demangles pointer to member functions for compat=4. This is not a problem for compat=5.

  Workaround: Recompile your program with:

  CC -compat=4 -Qoption ccfe -abiopt=pmfun1
  

  This flag introduces an ABI change and should not be used in production builds.



• On V9/V9 systems, stack traces that pass through code compiled with both the -g and -O options provide inaccurate results if the arguments are NOT integral types. Printing of float parameters in such functions may display the following error message:

  RegSet::getd('o1'): cannot -- will return 0.0
  

  Workaround: Use -g only.

• On V9/V9 systems, use of the call command or printing function calls is not working with nested small structure as an argument or as a return value.



• Using older copies of libC.so.5 or libC.so.4 may cause problems for dbx in the area of C++ exceptions. Warning messages about bad stabs and unhandled exceptions may result.

  Workaround: Install the latest libC.so.5 on all systems.

• Fortran users should compile with the -stackvar option to take full advantage of runtime checking.

  Some programs may not work properly with -stackvar. In such cases, try the -C compiler option, which will turn on array subscript checking without RTC.

• Follow fork may be unreliable for multithreaded applications.



• Use of the call command or printing function calls may cause deadlock situations with multithreaded applications.



• Do not use the fix and continue feature of dbx to change a header file if the file was part of a pre-compiled header (PCH) collection.



• The dbx command line interpreter is an older version of the Korn shell (ksh) that does not support Code Set Independence (CSI). Multi-byte characters can be misinterpreted when typed on the dbx command line.

---

G. Documentation Errata

There is no new information at this time. Additional information might be made available at http://developers.sun.com/sunstudio/

 

---

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