Re: Pure virtual function call in Winamp?
* Robbie Hatley:
I was playing a Cat Stevens song in Winamp just now, and I got this
error message, which popped up about 40 times, about 1 second apart:
What's up with that? I'm guessing this program tried to call a
pure-virtual member function of a base class directly, rather than
through an object of a derived class that actually defines the
function in question? I have a hard time imagining how that could
happen in production code... but it did. Any speculations on how
this kind of error can arise?
(Off-topic bonus question, just for fun: See if anyone can
identify the building in the background.)
I think it's possibly due to some malware, but most probably a Windows update,
infesting your system during the last 7 days.
It has nothing to do with WinAmp specifically; it's something affecting the
Microsoft C++ runtime DLL.
Unfortunately it also got me.
Reason for my belief regarding cause: every Windows update breaks some existing
functionality in old versions of Windows. On my XP prof, for example, ftype and
netstat and openfiles commands were broken by different updates. I think that is
by design (the netstat thing was provably by design, t'was documented). Sort of
Microsoft's way of saying "Hey, move on, we need to sell upgrades and we
absolutely don't want to shelve out good $$$ on supporting old versions!".
By the way, if you're using AVG anti-virus and/or have installed some Python
tools these last days then that would be something in common with me, but I
really do think it's much more likely a Windows update is the cause.
Cheers & hth.,