Groups | Blog | Home
all groups > dotnet clr > february 2007 >

dotnet clr : SOS Command not working



johnxhc NO[at]SPAM gmail.com
2/15/2007 12:30:51 PM
I am trying to use sos extension but almost half of the sos command do
not work, for example


0:027> !findtable
No export findtable found
0:027> !bpmd
No export bpmd found
0:027> !GCHandleLeaks
No export GCHandleLeaks found
0:027> !GCHandles
No export GCHandles found
0:027> !GetWorkItems
No export GetWorkItems found
0:027> !LoadCache
No export LoadCache found
0:027> !SaveAllModules
No export SaveAllModules found
0:027> !TraverseHeap
No export TraverseHeap found
0:027> !SaveCache
No export SaveCache found
0:027> !SaveModule
No export SaveModule found
0:027> !SearchStack
No export SearchStack found
0:027> !SyncBlk
0:027> !VerifyHeap
No export VerifyHeap found
0:027> !X
No export X found
0:027> !Analysis
No export Analysis found
0:027> !Bp
No export Bp found
0:027> !CheckCurrentException
No export CheckCurrentException found
0:027> !ConvertTicksToDate
No export ConvertTicksToDate found
0:027> !ConvertVTDateToDate
No export ConvertVTDateToDate found
0:027> !CurrentExceptionName
No export CurrentExceptionName found
0:027> !DumpAllExceptions
No export DumpAllExceptions found
0:027> !DumpBuckets
No export DumpBuckets found
0:027> !DumpCollection
No export DumpCollection found
0:027> !DumpConfig
No export DumpConfig found
0:027> !DumpLargeObjectSegments
No export DumpLargeObjectSegments found
0:027> !DumpLog
No export DumpLog found

Also, after I set a breakpoint (bring up the source code ) a managed
code, the program just does not break.

Any ideas?
Thanks in avance.
John



0:027> .chain
Extension DLL search Path:
C:\Program Files\Debugging Tools for Windows\winext;C:\Program
Files\Debugging Tools for Windows\winext\arcade;
C:\Program Files\Debugging Tools for Windows\WINXP;C:\Program Files
\Debugging Tools for Windows\pri;
C:\Program Files\Debugging Tools for Windows;C:\Program Files
\Debugging Tools for Windows\winext\arcade;
C:\Program Files\Debugging Tools for Windows
Extension DLL chain:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\sos: API 1.0.0, built
Wed Jul 14 23:46:07 2004
[path: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\sos.dll]
dbghelp: image 6.6.0007.5, API 6.0.6, built Sat Jul 08 13:11:32
2006
[path: C:\Program Files\Debugging Tools for Windows
\dbghelp.dll]
ext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 13:10:52 2006
[path: C:\Program Files\Debugging Tools for Windows\winext
\ext.dll]
exts: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 13:10:48 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP
\exts.dll]
uext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 13:11:02 2006
[path: C:\Program Files\Debugging Tools for Windows\winext
\uext.dll]
ntsdexts: image 6.0.5457.0, API 1.0.0, built Sat Jul 08 13:29:38
2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP
\ntsdexts.dll]
Willy Denoyette [MVP]
2/15/2007 10:33:28 PM
[quoted text, click to view]

Most of these are NOT sos commands, type !help to get a full list of available commands.
Note also that you should load sos.dll after the mscorwks.dll has been loaded in the
(managed) process.

Willy.


Oleg Starodumov
2/16/2007 12:00:00 AM

[quoted text, click to view]

You are using the old version of SOS (that came with the .NET framework itself).
Consider using the newer version that comes with WinDbg, in clr10 subdirectory -
that's the one that contains those commands.

[quoted text, click to view]

AFAIK live source level debugging is not possible with SOS
(you have to work on disassembly level and use SOS commands to see
where you are in the sources).

--
Oleg
[VC++ MVP http://www.debuginfo.com/]


AddThis Social Bookmark Button