Refreshing Debugger editors after moving separate debug files

Technote (troubleshooting)


Problem(Abstract)

In some cases when debugging programs where separate debug files have been moved from their default location, the Debugger Editor or Source Not Found Editor may not refresh correctly. If this situation occurs, these editors appear to display the wrong source file content.

Cause

Moving separate debug files from their default location.

Resolving the problem

The Debugger Editor or Source Not Found Editor can be manually refreshed by right-clicking the stack frame in the Debug View and selecting Lookup Source from the pop-up menu.

To prevent this from occurring, right-click the debug target, thread, or stack frame and select Edit Source Lookup from the pop-up menu. In the Edit Source Lookup Path dialog box, click Add. In the resulting Add Source dialog box, choose Debug engine path from the selection list. In the resulting dialog box, edit the debug engine path and enter one or more partition data sets (PDS) that contain(s) the separate debug files. This information will help the debugger automatically locate the separate debug files, and prevent the editor refresh problem.

Note that changes to the debug engine path will only take effect on the next debug session.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Debuggers
IBM WebSphere Developer Debugger for zSeries

Software version:

6.0.1

Operating system(s):

Windows 2000 Advanced Server, Windows 2000 Professional, Windows 2000 Server, Windows XP Pro

Reference #:

1225919

Modified date:

2009-10-27

Translate my page

Machine Translation

Content navigation