directorywindbgcode-organization

how deeply can the source path in windbg be nested?


If I have multiple binaries whose sources are scattered in various subfolders of an overlaying folder, would windbg have access to them if only the topmost folder was included in Source Path? As opposed to having to reference each project folder of each relevant binary separately.

Assuming, of course, that the sources are unique in the mentioned folder structure, i.e. there are no multiple versions of one and the same project, source, etc.


Solution

  • If you specify the parent folder for the source files in source path then it should traverse through the subdirectories to find the source files.

    Note that it will perform a signature match against your source files, in the same way that Visual studio will complain that the source files are different to the loaded dlls.

    The relative locations of the source files must match the original locations so if your source files are located in a different structure then you will need to do a manual load/browse to specify the location of the source files.