NonStop Development Environment for Eclipse 4.0 Debugging Supplement

2 Debugging tasks
Preparing to debug a NonStop Application
The standard process to prepare to debug a NonStop Application is:
Create a NonStop Local project or NonStop Remote project for the application
NOTE: Eclipse workspaces are containers for organizing a set of related projects. HP
recommends that you use separate workspaces for:
Local NSDEE projects and remote NSDEE projects
Each application
If your workspace combines multiple applications, HP recommends that you clear all breakpoints
and watch expressions before you debug each application.
Build a debuggable version of your application so that you can step through source and
examine symbols
For information about these tasks, see the NonStop Development Environment for Eclipse 4.0 User
Guide.
NOTE:
NSDEE also supports debugging applications built outside of NSDEE, referred to in this document
as projectless debugging.
Before you can debug a NonStop Application, you must build a debuggable version of your
application so that you can step through the source and examine symbols. For information, see
the NonStop Development Environment for Eclipse 4.0 User Guide and “Debugging optimized
code” (page 8).
Related topics
Related tasks:
“Launching a NonStop Application under debugger control” (page 9)
Attaching the debugger to a NonStop process” (page 10)
“Debugging a Snapshot file” (page 11)
See also the NonStop Development Environment for Eclipse 4.0 User Guide.
Debugging optimized code
If the application or any project it references has been compiled at an optimization level 1, the
Variables view might not be able to display the values of all local variables each time your
application is suspended. Figure 1 (page 9), which contains an example of the Variables view
for an application compiled at optimization level 1, shows the most common message displayed
for a variable that is unavailable due to code optimization:
Value not available at the current location\Unable to create variable
object
8 Debugging tasks