Repackaged VC9 SP1 Hotfix For The vector> Crash

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

grmileka — Thu, 07 May 2009 21:25:05 GMT

njoubert,

Yes, the new QFE has an updated version of all the VC redistributables (vcredist_*.exe, msms and dlls).

George Mileka

Visual C++ Libraries

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

njoubert — Thu, 07 May 2009 14:21:32 GMT

Is there a re-distributable available for the newer runtimes?

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

stu — Mon, 06 Apr 2009 06:45:15 GMT

Wow - that's some Super-Deluxe support anon is getting... Is anon really billg?

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

Stephan T. Lavavej [MSFT] — Mon, 30 Mar 2009 20:38:06 GMT

[njoubert]

> There still seems to be a problem with the tr1::result_of machinery.

(This wasn't affected by the hotfix.) Thanks for the bug report. It's Dev10#641210 in our internal database, currently assigned to me. It won't be fixed in VC10 Beta 1, but (no promises) I believe that we'll be able to fix it in Beta 2.

[anon]

> This hotfix seems to make intellisense always freeze the editor for a

> few seconds when typing an identifier. Anyone know how to fix it?

I talked to one of our Intellisense testers, and we're not sure what's going on here. (This hotfix affects the libraries only, not Intellisense.) Our best guess is that your NCB file has gotten corrupted. Try closing the IDE, deleting your NCB file, and seeing if the problem goes away.

If it doesn't, please E-mail me at stl@microsoft.com , and I'll put you in touch with the right people.

Stephan T. Lavavej

Visual C++ Libraries Developer

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

anon — Fri, 27 Mar 2009 20:58:50 GMT

This hotfix seems to make intellisense always freeze the editor for a few seconds when typing an identifier. Anyone know how to fix it?

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

njoubert — Fri, 27 Mar 2009 17:48:49 GMT

Thanks for the re-release, it certainly helps with a number of pieces of code I have.

There still seems to be a problem with the tr1::result_of machinery. The following code fails to compile, but it should (it does with boost). It seems to add a reference to all the arguments its passed.

#include <functional>

template <class T>

struct some_nested_result {

template <class>

struct result;

template <class Func>

struct result<some_nested_result(Func)> {

typedef typename

std::tr1::result_of<Func(T)>::type

type;

};

int main()

{

typedef std::tr1::function<int (int)> f;

typedef std::tr1::result_of<some_nested_result<int>(f)>::type

type;

return 0;

}

I've posted a connect issue on this.

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=425054

Should have some feedback shortly. Thanks again for all the effort getting TR1 in to MS.

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

Jalf1 — Fri, 27 Mar 2009 15:50:23 GMT

@Leo: Probably it took 3 months because these days, their installers have become pretty much the most complicated (and slowest) product MS has. C++ compilers and operating systems are trivial compared to the way they make installers... ;)

Although of course, I can hardly blame the VC++ team for that... :)

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

SvenC — Thu, 26 Mar 2009 11:41:53 GMT

Hi dvy,

this KB article might help:

http://support.microsoft.com/kb/925336

SvenC

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

dvy — Thu, 26 Mar 2009 11:20:46 GMT

I have VS2008 failed install!!

failed message:

MSI (s) (28:AC) [15:53:49:447]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (28:AC) [15:53:49:497]: End dialog not enabled

MSI (s) (28:AC) [15:53:49:497]: Original package ==> C:\WINDOWS\Installer\2873d25.msi

MSI (s) (28:AC) [15:53:49:497]: Package we're running from ==> C:\WINDOWS\Installer\2873d25.msi

MSI (s) (28:AC) [15:53:49:737]: APPCOMPAT: looking for appcompat database entry with ProductCode '{80C06CCD-7D07-3DB6-86CD-B57B3F0614D8}'.

MSI (s) (28:AC) [15:53:49:737]: APPCOMPAT: no matching ProductCode found in database.

MSI (s) (28:AC) [15:53:49:747]: MSCOREE not loaded loading copy from system32

MSI (s) (28:AC) [15:53:50:108]: Opening existing patch 'C:\WINDOWS\Installer\223472d.msp'.

MSI (s) (28:AC) [15:53:50:118]: Opening existing patch 'C:\WINDOWS\Installer\2234730.msp'.

MSI (s) (28:AC) [15:53:50:118]: Opening existing patch 'C:\WINDOWS\Installer\223472f.msp'.

MSI (s) (28:AC) [15:53:50:118]: Opening existing patch 'C:\WINDOWS\Installer\223472e.msp'.

MSI (s) (28:AC) [15:53:50:138]: Machine policy value 'AllowLockdownBrowse' is 0

MSI (s) (28:AC) [15:53:50:138]: Machine policy value 'DisableBrowse' is 0

MSI (s) (28:AC) [15:53:50:138]: File will have security applied from OpCode.

MSI (s) (28:AC) [15:54:24:167]: Original patch ==> d:\d66c505f428edcefd3abbe7c178ae6\VS90SP1-KB962219-x86.msp

MSI (s) (28:AC) [15:54:24:167]: Patch we're running from ==> C:\WINDOWS\Installer\41d7a.msp

MSI (s) (28:AC) [15:54:25:248]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'd:\d66c505f428edcefd3abbe7c178ae6\VS90SP1-KB962219-x86.msp' against software restriction policy

MSI (s) (28:AC) [15:54:25:248]: SOFTWARE RESTRICTION POLICY: d:\d66c505f428edcefd3abbe7c178ae6\VS90SP1-KB962219-x86.msp has a digital signature

MSI (s) (28:AC) [15:54:26:079]: SOFTWARE RESTRICTION POLICY: SaferIdentifyLevel reported failure. Assuming untrusted. . . (GetLastError returned 5)

MSI (s) (28:AC) [15:54:26:089]: The installation of d:\d66c505f428edcefd3abbe7c178ae6\VS90SP1-KB962219-x86.msp is not permitted due to an error in software restriction policy processing. The object cannot be trusted.

re: Repackaged VC9 SP1 Hotfix For The vector> Crash

Leo Davidson — Thu, 26 Mar 2009 10:32:03 GMT

Why did it take over three months to fix the fix, especially if it was just an error with the packaging/installer?

"Long test cycles" don't seem like a good reason considering the bugs which still slip through (e.g. the first fix not working).

I wish MS would react to these problems more rapidly. By all means take time to do a good amount of testing, but testing for three months gives you diminishing returns and still does not (and cannot) find all the problems. It's inevitable that problems will slip through occasionally and when they do we shouldn't have to wait *another* three months for them to be fixed.

If this was the only example of a fix-fix taking three months (or more) then I'd assume something just went wrong and wouldn't complain but it seems to be a common occurrence across multiple Microsoft products.

I'm not having a go at the VC team in particular as it's not just them. MS as a whole really need to improve on how they do testing and releases. And that may mean testing *less* and being prepared to deal with problems quickly.

Other examples which spring to mind: The amount of time it took for the data corruption bug in Windows Home Server -- which was known about when it was still in beta -- to be solved (one year). Or the way the mid-2008 Vista Media Center roll-up regressed back to XP's behaviour of unpausing/restarting video when the screen saver kicked in, which was not fixed for three months, and when a fix finally arrived it didn't actually fix all occurrences of the problem (we're still waiting!).