Set up the development and target environments for interactive debug
The packager control panel provides three controls to set up the development and target environments for interactive debugging.
Enable remote debugging
From the Transcript pull down the XD menu and choose Enable Remote Debugging. This can also be done in the passive image through the same pulldown menu in the XD Transcript.
Establish a connection between the development and target environments
The interactive debugging facility requires that a connection be set up between the workstation with the development image and the target system where the packaged image runs. Usually this is a TCP/IP connection.
To establish this connection, you must include the interactive debug TCP/IP feature, ‘Interactive Debug using TCP/IP’ in the passive image.
You can either add the feature to the passive image when you create the passive image, or you can alter the passive image after creation:
1. From the XD menu of the XD Transcript, select Image Properties.
2. From the Installed Features list of the Image Properties window, select Interactive Debug Using TCP/IP, and select Apply.
Tell the remote debugger what workstation to open
Tell the remote debugger where to open by setting the internet protocol (IP) address of workstation running the
development image. The
debugger is triggered by execution of the reduced image on the
target machine. It is actually opened on the workstation running the
development image.
In the passive image, choose Set Workstation Address… from the XD Transcript XD pulldown menu, and then enter the internet protocol address of the development image.
The examples are based on the development image being the same as the one used to package the example code. This is the best situation to have. However, if the image used to package the runtime is no longer present, the interactive debugger can still be opened in a reconstructed development image. Considerations in building that image are
o The prerequisites to headless application must be loaded in the development image
o The development image must have a passive image
matching the target environment of the headless application
with the headless application loaded.
Set image startup class
The image startup class of the packaging instructions should be AbtInteractiveDebugStartup.
Last modified date: 05/17/2019