CompuServe Messages

Hi Juergen, thanks for your comments 1) The debug information that Zortech puts out is CodeView 3.0 style, which has no defined debug records for classs information. The next version of Symantec's C++ will produce CodeView 4.0 information, so all class information will be available. 2) Unfortunately, inline code (or #included code) cannot be traced through in this version, also mostly due to restrictions in the debug information. This will also be remedied in the next release. 3) If you step into a function, then press "return from call", it will not have built the stack fram correctly yet, and will return one level too high. This should not be the case once you've stepped deeper into the procedure. Another reason this might happen is code-optimization. Be sure not to optimize your code for debugging. Most of these problems are related to both how the compiler generates debug information, and how it is interpreted by the debugger. I would wait until the next version comes out, with which all of these restrictions will be resolved. As long as WatCom generates CodeView information, MultiScope will debug it. However, the current versions of MultiScope will only debug 16bit applications. Please let me know if you have any other questions. Sincerely, Oliver Vogel Symantec – MultiScope Product Support