Walter Bright Wrote: > ws wrote: > > Here is what i did: > > > > c:\>windbg winsamp.exe Press F5 to start running, then just close the > > winsamp.exe. > > > > Couple of secs later windbg crashed with 'The instruction at > > 0x731444fe referenced memory at 0x00000000...' while it is unloading > > the system modules. > > > > winsamp.exe is built from the win32 sample verbatim, and windbg.exe > > is provided by dmd compiler package. > > > > I am using win XP and both dmd 2.019 or dmd 1.034, so guess it is not > > dmd version specific. Am I the the only one seeing this? > > When MS updated XP, they broke windbg maybe a year ago. The same windbg > now always fails on exit. Fortunately, it doesn't fail before you debug > your program, just on exit. > > I don't think there's anything I can do about this.
Ah, finally I found the culprit! It is the unlocker.exe running in the background, and that crashes windbg running D windows app consistently when it exits. (does not affect the console app). Took me a long time to find out. Thanks for your concerns!
