Since the issue is in SymProxy and a Microsoft representative told you he's looking at the issue, I don't think this warrants any change. Think about all the other non-Windows symbol servers that are broken at the moment...
Hint: pre-cache the data, you won't have any problem afterward. M-A On Fri, Apr 3, 2009 at 4:22 PM, ptr727 <pieter.vilj...@gmail.com> wrote: > > Hi, I noticed that the Microsoft Symbol Proxy Server, SymProxy, can't > retrieve symbols from Chrome or Firefox debug symbol servers. > > As background, SymProxy is a single point symbol server for developers > inside an organization, and will retrieve symbols from multiple > internal or external symbol servers: > http://msdn.microsoft.com/en-us/library/cc901417.aspx > http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx > > It turns out the problem is that SymProxy makes the URI all lowercase, > and I assume the Google and Firefox symbol server web frontends are > Linux based and case sensitive. > > So this is a bit of a problem, can Firefox and Google make their > symbol servers not case sensitive, or can Microsoft change SymProxy to > not change the URI case? > > Here is my post about the problem on the Microsoft newsgroups: > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windbg&mid=1f33aec5-d8d0-47cc-bdc4-e2a60d028ef6 > > Has anybody else experienced similar problems? > Any other ideas to work around the problem? > > P. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
