Thursday Mar 27, 2014

Solaris Studio 12.4 Beta is live

The Oracle Solaris Studio 12.4 Beta release is out. Oracle Solaris Studio is a suite of compilers and code analysis tools that assist developers in creating highly optimized, robust, and secure applications for the Oracle Solaris and Linux Operating Systems. These tools help application developers achieve the best performance on Oracle's newest T-series and M-series SPARC servers, Fujitsu's M10 servers, and Intel-based servers. 

New features and enhancements in Oracle Solaris Studio 12.4 include:

  • New C++ compiler and dbx debugger that support the C++ 2011 language standard
  • A completely redesigned Performance Analyzer UI that simplifies identification of key performance issues, plus remote data analysis, cross-architecture support, comparison of results, and improved kernel profiling
  • Code Analyzer for improving your application with static source-code checking, run-time memory access checking (including memory leaks), and identification of un-exercised code. Graphical user interface and command-line provide robust interfaces for reviewing results and historical analysis of data
  • Compiler and library optimizations for Oracle's SPARC T5, M5, M6, Fujitsu's M10, and Intel's Ivy Bridge and Haswell servers
  • Support for new OpenMP 4.0 standard including Region Cancellation, Thread Affinity, Tasking Extensions and Sequentially Consistent Atomics
  • Integrated Development Environment (IDE) that includes C++ 2011 support, improved response time, and a smaller memory footprint to efficiently handle very large source repositories.

Visit the Oracle Solaris Studio 12.4 Beta homepage and download the Beta release today!

Tuesday Jul 19, 2011

Investigating Memory Leaks with Dtrace

This article shows a real case of DTrace framework usage to detect undeleted objects in a C++ application running on Solaris 10. In this case context, undeleted objects refer to temporary business objects that are explicitly created, with the new() operator, but never destroyed. This behavior, comparable in its effects to the so-called memory leak1, may lead to a significant unwanted increase in memory usage and cause paging activity on the system, or even generate new objects creation failures with applications which create objects iteratively.

Since the non-deletion of these business objects is not the result of bad pointers but rather of an incorrect cache management in the application, specialized memory-leaks tracking tools which look after allocated memory chunks-pointers inconsistencies do not detect this type of undeleted objects. For instance, Oracle Solaris Discovery tool2 or Oracle Solaris libumem audit facility3, as well as Rational Purify or gdb are ineffective in this situation4.

A new tool based on DTrace and perl scripts was developed to address this specific need and is usable with all programs that have iterative objects creation and deletion patterns similar to our case described below. The tool requires no binary change and is easy to use. It has demonstrated its efficiency at a customer site on a pre-production system in finding the leak in a couple of minutes, where the traditional methods failed after days of investigations.

Authors: Pascal Danek, Reuters Financial Software, France - Claude Teissedre, Oracle France

[Read More]

Monday May 23, 2011

Leveraging a disaster recovery site for development - Part 2

In our previous post, we introduced the idea of using Disaster Recovery (DR) sites as a private cloud for hosting virtual development and testing environments. The solution we developped for an ISV partner of ours in the Healthcare sector looks like this.


The solution is based on the Zones and ZFS features of Oracle Solaris --available from Solaris 10 and up. Solaris Zones (a.k.a. Containers) are an operating system level virtualization technology that…

[Read More]

Monday May 09, 2011

Leveraging a disaster recovery site for development - Part 1

As part of the software development lifecycle, the application testing environments are often overlooked and mostly left to the appreciation of each developer, who routinely end up using their own PC or laptop for that. The main advantage here is that it gives developers full control on the testing environment without interfering with other developers or worse, with the production system.

There are however some serious drawbacks with this method:

  • Installing and configuring the various layers of software is time consuming and unproductive. Not to mention that developers (rightfully) test a lot by messing around with their environment or data, so the burden of installing and configuring is a repeating one.
  • Developers are unable to leverage and test the scalability of their code on the hundreds of threads that modern production servers offer.
  • Copying hundreds of gigabytes from the production database to every laptop is not an option, leaving the developers test their code on small, often outdated, data sets.

With the advent of virtualization, using ready-to-boot virtual images of a fully pre-installed and configured application testing environment on an internal cloud has become…[Read More]

Friday Jul 31, 2009

HAR source code up on

The HAR 2.x source code has been published today --I apologize for the delay-- and is now available under the CDDL 1.0 license on Project Kenai, a collaborative hosting site for open-source projects sponsored by Sun Microsystems. HAR users are encourage to join the discussion --whether on the wiki or mailing lists-- there.

If you feel like checking out --and why not, contributing to-- the HAR code, note that Subversion was selected as the version control system; the Subversion URI is If you are not very familiar with Subversion and do not have yet a preferred IDE, NetBeans 6.x comes in with a built-in integration with Subversion. Basically, if the Subversion client is already installed on your system --try which svn on a Unix-like system--, just select Tools->Subversion->Check Out... in NetBeans --have your Kenai login and password handy.

Below is a snapshot of what you should be ending with.


How open innovation and technology adoption translates to business value, with stories from our developer support work at Oracle's ISV Engineering.



« July 2016