AE Debug Dr. Watson does work in XPE

[Thomas Bach Petersen]

I have the exact same problem and tried the same as you,
so my short question is - did you solve your problem and
if so - how?

I have read through all the registry settings for the
disabling Error Reporting tool and for enabling
application debugging - in my best believe all my
settings are correct, but it still doesn't work.

I made a small program that provoke a memory violation
crash (mycrash.exe) - and every time it crashes XPE
automatically start a program called "dwwin.exe" which is
the client of the windows reporting tool.

I have searched quite a lot but have found no solution.

I have tried to rename dwwin.exe and copy drwtsn32.exe to
dwwin.exe. When a crash occur Dr. Watson's setup GUI come
up - just as if you started drwtsn32.exe from start | run.

My ugly workaround will be to try and see what parameters
are being supplied to dwwin.exe and if the "process id"
is being supplied then make a program or script that
calls drwtsn32.exe with "-p <proves id>" parameter to
force Dr. Watson to store a crash dump file.

Virtually,
Thomas

-----Original Message-----
Hi everybody,

I want to use a JIT-Debugger on XPE, but neither drwtsn32 nor the debugging
tools for windows works. The regestry-Key AeDebug is correct(works under
XPPro).
If an error occurs, the "send error report wizard" pops up, even if I
disable it in System Properties.

Thanks for your help.
Cons


.

..

 

[Mark K Vallevand]

Cut and past from my process doc:



Create a DrWatson component using the steps below. Ensure that you select
the following repository for this component: "Windows XP Embedded Client
(x86) Service Pack 1".



A. Using Component Designer, create a new document, open the tree,
right click on Components and add a new component.

B. Fill component properties.



C. Add the file resource (right click on Files):

DRWTSN32.exe to %11%



4.. Add a component Dependency (right click on Component or Group
Dependancy):
Primtive: Dbgeng.dll



5.. Add the following registry data (right click on Registry Data):
Registry Path
Value Name
Format
Value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson DumpAllThreads
reg_dword
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
AppendToLogFile
reg_dword
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
VisualNotification
reg_dword
0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
CreateCrashDump
reg_dword
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
Instructions
reg_dword
10

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
MaximumCrashes
reg_dword
10

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
CrashDumpType
reg_dword
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
SoundNotification
reg_dword
0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
WaveFile
reg_sz


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
CrashDumpFile
reg_sz
C:\Documents and Settings\All Users\Application
Data\Microsoft\DrWatson\user.dmp

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson
LogFilePath
reg_sz
C:\Documents and Settings\All Users\Application Data\Microsoft\DrWatson

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\AeDebug
Auto
reg_sz
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\AeDebug
Debugger
reg_sz
drwtsn32 -p %%ld -e %%ld -g

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\IniFileMapping\win.ini
AeDebug
reg_sz
SYS:Microsoft\Windows NT\CurrentVersion\AeDebug




F. Save the component as DrWatson.sld.



G. Import the DrWatson component into the Component Database using the
Component Database Manager:

1.. On the Database tab, choose Import.
2.. In the SLD File list, browse to the component DrWatson.sld file and
choose Open.
3.. Choose Import.