Search found 5 matches

by rplaire
Mon Apr 11, 2016 8:12 pm
Forum: Using .NET Memory Profiler
Topic: Download MSCORDACWKS.dll from MS doesn't work
Replies: 4
Views: 10818

Re: Download MSCORDACWKS.dll from MS doesn't work

Ah, now I understand, such a feature would be obviated by not having the SOS dependency. I look forward to the beta!
by rplaire
Mon Apr 11, 2016 1:47 am
Forum: Using .NET Memory Profiler
Topic: Download MSCORDACWKS.dll from MS doesn't work
Replies: 4
Views: 10818

Re: Download MSCORDACWKS.dll from MS doesn't work

I see, I thought SOS.dll would also be downloaded, since WinDbg does this, as can be seen in the log lines: SYMSRV: SOS_x86_x86_4.6.1073.00.dll from https://msdl.microsoft.com/download/symbols: 279666 bytes - 0 percentSYMSRV: Waiting for the server to respond to a request. ... DBGHELP: C:\ProgramDat...
by rplaire
Wed Apr 06, 2016 1:52 am
Forum: Using .NET Memory Profiler
Topic: Download MSCORDACWKS.dll from MS doesn't work
Replies: 4
Views: 10818

Download MSCORDACWKS.dll from MS doesn't work

.NET Runtime Version Mismatch_NetMemProfiler_(1466).png The dump import dialog which allows selection of a matching MSCORDACWKS.dll doesn't appear to ever successfully download the correct version from MS symbol servers. When I use WinDbg's .cordll -ve -u -l command, the correct version is found an...
by rplaire
Wed Apr 06, 2016 1:40 am
Forum: Using .NET Memory Profiler
Topic: mscordacwks.dll from target machine not accepted
Replies: 2
Views: 8088

Re: mscordacwks.dll from target machine not accepted

Yea, that was it. I was confused that that field was not optional since the "OK" button was active while the SOS field was unfilled.
by rplaire
Wed Feb 17, 2016 9:10 pm
Forum: Using .NET Memory Profiler
Topic: mscordacwks.dll from target machine not accepted
Replies: 2
Views: 8088

mscordacwks.dll from target machine not accepted

Greetings, I have a dump from a target machine which requires mscordacwks.dll 4.6.1063.1 32 bit. I obtained this dll and sos.dll and the prompting dialog will not accept it to open the dump. When I click "Ok" the dialog reappears. Why is this? What can be done to convince Memprofiler I have the righ...