View mode: basic / threaded / horizontal-split · Log in · Help
March 12, 2009
winsamp sample crashed windbg
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?
March 12, 2009
Re: winsamp sample crashed windbg
windbg from mars is quite outdated, you're advised to upgrade it.
March 12, 2009
Re: winsamp sample crashed windbg
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.
March 12, 2009
Re: winsamp sample crashed windbg
Don Wrote:

> Later versions don't work.

At all?
March 14, 2009
Re: winsamp sample crashed windbg
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.
March 15, 2009
Re: winsamp sample crashed windbg
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!
March 15, 2009
Re: winsamp sample crashed windbg
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 ?
March 15, 2009
Re: winsamp sample crashed windbg
On Sun, Mar 15, 2009 at 10:46 AM, Walter Bright
<newshound1@digitalmars.com> 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 to find out.
>> Thanks for your concerns!
>
> What's unlocker.exe ?
>

Google seems to suggest it's a Worm virus...
A virus scan is probably in order!
March 16, 2009
Re: winsamp sample crashed windbg
Tomas Lindquist Olsen Wrote:

> On Sun, Mar 15, 2009 at 10:46 AM, Walter Bright
> <newshound1@digitalmars.com> 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 to find out.
> >> Thanks for your concerns!
> >
> > What's unlocker.exe ?
> >
> 
> Google seems to suggest it's a Worm virus...
> A virus scan is probably in order!

It is a explorer extension + system tray util that pops up whenever you try to delete a file/folder but get annoying messages from Windows like:
-Access is denied
-There has been a sharing violation.
-The source or destination file may be in use.
-The file is in use by another program or user..etc
It will list the exes/dlls that holds the corresponding file handle. Comes in handy many times.
Top | Discussion index | About this forum | D home