MS Source Server:srcsrv.ini 变量的意义
MS 源服务器技术使用名为 srcsrv.ini 的初始化文件。 其中一个值标识源服务器位置,例如,
MYSERVER=\\machine\foobar
文档对该值没有太多解答。 首先,我一直无法找到值名称的意义,即左侧的内容,而且我没有看到它在其他地方使用。 休沃特 高级 Windows 调试 中的 Pravat 说“左侧...代表项目名称”,但事实并非如此。似乎与 MS 的“MYSERVER”示例一致。
左侧的意义是什么? 它还用在什么地方? 该值是否引用服务器或项目,是每个服务器一个还是每个项目一个?
The MS source server technology uses an initialization file named srcsrv.ini. One of the values identifies the source server location(s), e.g.,
MYSERVER=\\machine\foobar
The docs leave much unanswered about this value. To start with, I haven't been able to find the significance of the value name, i.e., what's on the left side--and I don't see it used anywhere else. Hewardt & Pravat in Advanced Windows Debugging say "The left side ... represents the project name", but that doesn't seem to jibe with MS's "MYSERVER" example.
What is the significance of the left side? Where else is it used? Does the value reference a server or a project, and is there one per server, or one per project?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
对于未来关注此问题的任何人,我从 MS 收到了以下信息:
因此,它是源服务器的逻辑名称,并且可以在调试时更改其值以引用与创建 PDB 时最初使用的服务器不同的服务器。
For anyone looking into this in the future, I received the following information from MS:
So, it is a logical name for a source server, and its value can be changed at debug time to reference a different server than the one originally used when the PDBs were created.
调试器检索源代码的方式是通过 srcsrv 使用某些命令行实用程序。 实用程序本身和使用的命令行根据托管代码的存储库类型而有所不同。 阻止检索的问题之一是调用该命令行程序时会失败。
要了解为什么在 WinDBG 中使用命令 !sym busy。 它对于诊断符号服务器问题非常有帮助,但对于源索引 PDB,它还会显示实际使用的命令行 WinDBG。 从命令日志窗口复制命令并在 CMD.EXE 中运行它以获取有关故障的更多详细信息。
The way the debugger retrieves your source is by srcsrv using some command line utility. The utility program itself and the command line used varies depending on which type of repository hosts your code. One of the issues preventing retrieval is that when that command line program is invoked it fails.
To find out why use the command !sym noisy in WinDBG. It is mostly helpful in diagnosing symbol server issues but for source indexed PDB it also will show the actual command line WinDBG used. Copy the command from the command log window and run it in CMD.EXE to get more details on the failure.