0

I'm trying to get to the bottom of an annoying problem with EventViewer, so I've hooked up an instance of VS (2013) to mmc.exe and breaking on exceptions.

VS only gives me the disassembly, even though it's pointing at System.IO.Path.CheckInvalidPathChars(string), and the Modules window says that mscorlib.dll (2.0) is loaded with the symbol file (twice, as it happens, once in DefaultDomain, and once in EventViewer domain).

Failing that, could anyone help me work out what the offending Path is, starting from the Disassembly?

Benjol
  • 63,995
  • 54
  • 186
  • 268
  • 2
    Having symbols does not mean you have source. Symbols for a module just means a debugger can determine more information (eg. method name) from execution address. – Richard Jun 06 '16 at 13:20
  • @Richard, that's a shame. I'm pretty sure that sometimes I do end up stepping into code that is not mine, what is the extra sauce in that case? – Benjol Jun 06 '16 at 13:30
  • And couldn't it at least send me to ReferenceSource.microsoft.com? – Benjol Jun 06 '16 at 13:34
  • Source servers can be used, and there is inbuilt support (if enabled) to handle parts of the BCL source. [2nd comment] Enabling source server support, disabling my code (both in debugging options) will integrate BCL source debugging. – Richard Jun 06 '16 at 13:36
  • 1
    You are not going to get source code for .NET 2.0. It isn't that useful anyway, CheckInvalidPathChars() does not have a bug. Just check the argument passed to the method. – Hans Passant Jun 06 '16 at 13:42
  • @HansPassant, AH!, that's the missing detail, everything makes sense. It's not me passing the path in, unfortunately, that's the last part of the question... – Benjol Jun 06 '16 at 13:52

0 Answers0