Note that there are some explanatory texts on larger screens.

plurals
  1. POSetting up a public (or private) symbol server over http
    text
    copied!<p>Every piece of documentation I've found (references 1 through 5) talks about setting up a symbol server by using a shared UNC path, and then putting the correct settings available to the local debugger instance (whether _NT_SYMBOL_PATH or the Visual Studio IDE Debugging settings).</p> <p>Microsoft provides a symbol server (reference 6) available via http for their public symbol stores.</p> <p>I want to create, for my own code, a symbol server accessible over http transport, instead of over UNC file sharing. The Mozilla folks appear to have done so (reference 7), but it is no longer functional.</p> <p>Are there better references available for performing this task than I have found so far?</p> <hr> <p>References</p> <ol> <li><a href="https://msdn.microsoft.com/en-us/library/b8ttk8zy(v=vs.80).aspx" rel="noreferrer">https://msdn.microsoft.com/en-us/library/b8ttk8zy(v=vs.80).aspx</a> </li> <li><a href="http://msdn.microsoft.com/en-us/library/ms680693(v=vs.85).aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms680693(v=vs.85).aspx</a> </li> <li><a href="http://stackhash.com/blog/post/Setting-up-a-Symbol-Server.aspx" rel="noreferrer">http://stackhash.com/blog/post/Setting-up-a-Symbol-Server.aspx</a> </li> <li><a href="http://entland.homelinux.com/blog/2006/07/06/" rel="noreferrer">http://entland.homelinux.com/blog/2006/07/06/</a>… </li> <li><a href="http://msdn.microsoft.com/en-us/windows/hardware/gg462988" rel="noreferrer">http://msdn.microsoft.com/en-us/windows/hardware/gg462988</a> </li> <li><a href="http://support.microsoft.com/kb/311503" rel="noreferrer">http://support.microsoft.com/kb/311503</a> </li> <li><a href="http://developer.mozilla.org/en/Using_the_Mozilla_symbol_server" rel="noreferrer">http://developer.mozilla.org/en/Using_the_Mozilla_symbol_server</a></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload