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

"Ismo Salonen"  wrote in message 
news:epujyAA4HHA.1164@TK2MSFTNGP02.phx.gbl...

> 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


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

"PvdG42"  wrote in message 
news:ePjrurA4HHA.5776@TK2MSFTNGP04.phx.gbl...

> "Ismo Salonen"  wrote in message 
> news:epujyAA4HHA.1164@TK2MSFTNGP02.phx.gbl...
>> 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
>
> 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.

Ben Voigt [C++ MVP] wrote:

> "PvdG42"  wrote in message
> news:ePjrurA4HHA.5776@TK2MSFTNGP04.phx.gbl...
>> "Ismo Salonen"  wrote in message
>> news:epujyAA4HHA.1164@TK2MSFTNGP02.phx.gbl...
>>> 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
>>
>> 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.


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

-cd

Carl Daniel [VC++ MVP] wrote:

> Ben Voigt [C++ MVP] wrote:
>> "PvdG42"  wrote in message
>> news:ePjrurA4HHA.5776@TK2MSFTNGP04.phx.gbl...
>>> "Ismo Salonen"  wrote in message
>>> news:epujyAA4HHA.1164@TK2MSFTNGP02.phx.gbl...
>>>> 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
>>> 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.
> 
> Yes, it is.  You can develop with VS2003 on XP and then debug with VS2005 + 
> SP1 + VistaPatch on Vista.
> 
> -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