I suggest you ...

Add Source Indexer support for Microsoft Source Server (and Symbol Server)

First: I'm no expert on this, but this is how I understand it.

Debuggers (WinDbg and VS) on Windows use Symbol Servers for getting the correct .pdb file and Source Servers to get the correct source code while debugging a minidump. This enables debugging of code that you currently don't have in your workspace.

While Plastic SCM has no contact with Symbol Servers, it should have with Source Servers.
You may read about it here: https://docs.microsoft.com/en-us/windows/desktop/debug/source-server-and-source-indexing

In short:
Debuggers will ask the Symbol Server for the debugging symbols and then the Source Server for the source files.
To make this work the symbols have to be "source indexed".
Microsoft ships indexer scripts for TFS, Perforce, VSS, CVS and Subversion.

Plastic SCM should ship an indexer script, too =)
How to: https://docs.microsoft.com/en-us/windows/desktop/debug/source-server-and-source-indexing#creating-a-source-control-provider-module

3 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
SWSBB shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • AdminCodice Software (CEO / Founder, plasticscm) commented  ·   ·  Flag as inappropriate

    Hey, thanks for sharing this.

    I've been aware of these symbol servers for... like more than a decade (almost two now). I mean, I think they had a different name before.

    They are awesome anyway.

    I'd really (really) like to implement this.

    Do you know of anyone, any contractor, we could hire to implement this?? I mean, I'm not sure we'll have the time to do it ourselves here, but we can certainly pay someone to do it.



Feedback and Knowledge Base