| Product(s): | OpenRoads Designer |
| Version(s): | 10.00.00.120+ |
| Area: | Workspace |
| Original Author: | Holly Herring, Bentley Technical Support Group |
Question:
How do I interpret and use a msdebug.txt file to troubleshoot my workspace?
Answer:
Work through this wiki (for PW)on how to create the msdebug.txt file. (note: a program such as Notepad++ will be easier that Notepad to view this file)
This debug file gives you a detailed step-by-step look at how ORD loads and defines every variable within every cfg in order of process. This will help you determine how a variable is being overwritten, what is being defined and when it is being defined. It provides a single file to do a full search through your workspace. It helps to find those hard to find minor errors.
Here are some notes to interpret this:
- You will see "Processing macro file..." when a new cfg is loaded. Each line underneath is how each variable within the cfg is defined.
- The end of the file contains a Configuration Variable Summary that shows how every single variable is defined when all the cfgs have been read
You can use this file to do a word search for a specific variable. When that variable is found, you can scroll up until you see "Processing macro file..." to see which cfg it is being defined in. From there, you can know exactly where that cfg is, go open it, and make the necessary changes.