• Chapter 1: Getting Started with Stylus Studio®
  • Stylus Studio Editions
  • Starting Stylus Studio
  • Updating an XML Document-Getting Started
  • Working with Stylesheets - Getting Started
  • Stylesheets That Generate HTML - Getting Started
  • Using the XSLT Mapper - Getting Started
  • Debugging Stylesheets - Getting Started
    • Setting Up Stylus Studio to Debug Sample Files
    • Inserting a Breakpoint in the Sample Stylesheet
    • Gathering Debug Information About the Sample Files
      • The Variables Window
      • The Call Stack Window
      • The Watch Window
    • Ending Processing During a Debug Session
  • Defining a DTD - Getting Started
  • Defining an XML Schema Using the Diagram Tab - Getting Started
  • Opening Files in Stylus Studio
  • Working with Projects
  • Customizing Tool Bars
  • Specifying Stylus Studio Options
  • Defining Keyboard Shortcuts
  • Using Stylus Studio from the Command Line
  • Managing Stylus Studio Performance
  • Configuring Java Components
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Integrating with Third-Party File Systems
• Chapter 14: Extending Stylus Studio
• Chapter 15: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Gathering Debug Information About the Sample Files

Gathering Debug Information About the Sample Files

This topic is part of a sequence that starts with Setting Up Stylus Studio to Debug Sample Files.

When XSLT processing is suspended at a breakpoint, Stylus Studio displays the Variables, Call Stack, and Watch windows.

You can use the information in these windows to learn about potential and actual problems encountered in your XSLT processing.

The Variables Window

The Variables window displays a list of variables and their values when processing was suspended.

As you can see, the stylesheet defines the VideoName parameter, which had no value when processing was suspended. In addition, the Variables window shows you that when processing was suspended, the processor was operating on the first director child element of the first video child element of the first videos child element of the first result element.

The Call Stack Window

The Call Stack window displays a history of the steps the processor performed to reach the point at which processing was suspended, including the names of the templates that are currently instantiated, in most recent-to-oldest order.

In this example, the XSLT processor has instantiated the director template, which is part of the instantiation of the video template, which is part of the instantiation of the template that matches the root node.

To step out of debug, click Step out , or press Shift+F11.

The processor completes the instantiation of the director template, which adds some HTML to the Preview window. The yellow triangle moves to show the new location in the XSLT source.

As you can see in the Call Stack window, the processor is now two levels deep in the template that matches the root node, instead of three levels deep as it was previously. The value of the context node in the Variables window is /result[1]/videos[1]/video[9] (it was /result[1]/videos[1]/video[9]/director[1]).

The Watch Window

If your application contains a lot of variables, the Watch window allows you to focus on the variables in which you are particularly interested.

To enter a variable to watch:

As processing continues, the Watch window displays the values of the variables you specify.