Tomas Lindquist Olsen Wrote:
> On Sun, Mar 15, 2009 at 10:46 AM, Walter Bright
> wrote:
> > ws wrote:
> >>
> >> 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 t
On Sun, Mar 15, 2009 at 10:46 AM, Walter Bright
wrote:
> ws wrote:
>>
>> 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 t
ws wrote:
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!
What's unlocker.exe ?
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 0x...' while it is unloading
>
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 0x...' while it is unloading
the system modules.
winsamp.exe is built from the w
Don Wrote:
> Later versions don't work.
At all?
Kagamin wrote:
windbg from mars is quite outdated, you're advised to upgrade it.
Yes it's outdated, but don't upgrade it. Later versions don't work.
windbg from mars is quite outdated, you're advised to upgrade it.
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 0x...' while it is unloading the system modules.
winsamp.exe is built from the win32 samp
