Wierd problem with VS2003&vista

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ismo Salonen - 16 Aug 2007 13:23 GMT

I've got code that works when started normally (explorer, command
whatever) but fails when started from VS2003. It crashes in different
place when started with debugging (F5) and other place when started
without debugging ( CTRL+F5).

The same code works correctly on W2K/W2K3/XP. All modules are C++ code.

The Visual Studio 2003 must be currently used due to 3rd party
libraries. It has the SP1 installed.

Is the VS2003 debugger totally useless on Vista ?

When the program crashes I can attach it with debugger and always there
is secur32.dll!760621f4 as last address on stack.

Has anybody else seen this behaviour or is it just me ?

ismo

Reply to this Message

PvdG42 - 16 Aug 2007 14:39 GMT

> I've got code that works when started normally (explorer, command
> whatever) but fails when started from VS2003. It crashes in different
[quoted text clipped - 14 lines]
>
> ismo

VS .NET 2003 is not supported in Vista, and you've probably run into one of
the many reasons why.

Reply to this Message

Ben Voigt [C++ MVP] - 16 Aug 2007 14:54 GMT

>> I've got code that works when started normally (explorer, command
>> whatever) but fails when started from VS2003. It crashes in different
[quoted text clipped - 17 lines]
> VS .NET 2003 is not supported in Vista, and you've probably run into one
> of the many reasons why.

I believe I've heard that it was specifically the debugger that wouldn't run
right, and far too much trouble for MS to make it compatible.

However, I think the debug information created by 2003 should be usable from
2005 or WinDbg.

Reply to this Message

Carl Daniel [VC++ MVP] - 16 Aug 2007 15:04 GMT

>>> I've got code that works when started normally (explorer, command
>>> whatever) but fails when started from VS2003. It crashes in
[quoted text clipped - 22 lines]
> However, I think the debug information created by 2003 should be
> usable from 2005 or WinDbg.

Yes, it is. You can develop with VS2003 on XP and then debug with VS2005 +
SP1 + VistaPatch on Vista.

-cd

Reply to this Message

Ismo Salonen - 17 Aug 2007 06:32 GMT

>>>> I've got code that works when started normally (explorer, command
>>>> whatever) but fails when started from VS2003. It crashes in
[quoted text clipped - 25 lines]
>
> -cd

I've been banging my head against the wall with this, looking for
phantom bugs that appear only while debugging.
Running the debugger as administrator helps a little but I can not
trust debugger anymore on vista. Luckily next version will be compiled
with VS2005.

ismo

Reply to this Message

Wierd problem with VS2003&vista

Free Magazines