Help catching AV with WinDbg and ADPlus 7.0
- by Stoune
I want to catch Memory Access Violation in SQL Server Compact Edition like this described at
http://debuggingblog.com/wp/2009/02/18/memory-access-violation-in-sql-server-compact-editionce/
The suggested config is:
CRASH
Quiet
MyApp.exe
NoDumpOnFirstChance
clr;av
FullDump
gn
I download latest Debugging Tools and observe what Microsoft rewrite adplus tool into managed code and change syntax of config File.
I rewrite config file like this:
<ADPlus Version="2">
<Settings>
<RunMode>Crash</RunMode>
<Option>Quiet</Option>
<Option>NoDumpOnFirst</Option>
<Sympath>c:\symbols\</Sympath>
<OutputDir>c:\work\output\</OutputDir>
<ProcessName>c:\work\app\output\MyApp.exe</ProcessName>
</Settings>
<Exceptions><!--to get the full dump on clr access violation-->
<Exception Code="clr;av">
<Actions1>FullDump</Actions1>
<ReturnAction1>gn</ReturnAction1>
</Exception>
</Exceptions>
</ADPlus>
And I get error "Couldn't find exception with code: clr;av". If I understand right It didn't load sos extension, but I can't find the right section and syntax that I should use to load it.
adplus_old.vbs - for some reasons didn't launch process on Windows 7.
WinDBG 6.12.0002.633 X86
ADPlus Engine Version: 7.01.002 02/27/2009
Maybe someone has a working example of config of debugging .NET app with latest adplus.exe?
