Go to main content
Oracle® Developer Studio 12.5: Debugging a Program with dbx

Exit Print View

Updated: June 2016
 
 

Skimming Errors

You are depending on macro skimming if you did not compile your code with the –g3 option and have the macro_source dbxenv variable set to skim_unless_compiler or skim.

For skimming to succeed for a module, the following conditions need to be true:

  • The module must have been compiled with a Oracle Developer Studio compiler using the –g option.

  • The compiler used to compile the module must be accessible by dbx.

  • The source file for the module must be accessible by dbx.

  • Files included by the source code of the module must be available, that is, the path given to the –I options when the module was compiled must be accessible by dbx.

  • The source code must be lexically sound. For example, it cannot contain unterminated strings of comments or be missing #endifs.

If the source code or include files are not accessible by dbx, you can use the pathmap command to make them accessible.