If anyone uses the Microsoft symbol server ...

[onomatopoeia]

then it's probably best to avoid Windows update at the moment.

Microsoft pushed a new ntdll.dll (windows 7, x64) live end of last week sometime without putting the accompanying symbols on msdl.microsoft.com. Anyone that uses windbg will find it doesn't work nearly as well if they get the new ntdll.dll, as I did this afternoon.

 

[arad85]

Ooops... Not used windbg much.. are you left trawling x86 assembly code now?

 

[onomatopoeia]

Yes, but I write assembly language when it's appropriate (lots of it in this project) so that isn't a problem - it's the lack of symbols for all the internal functions in the kernel and the fact that some of the nice things windbg does (like parse out the process information block and loaded modules etc) break if the internal symbols are missing.

Had a frustrating afternoon today debugging why the debugger wasn't working properly!