MSVC++ 6.0 windbg

WINDBG
1

I’m having strange problems with the newer windbg that works with MSVC++ 6.0
in that the stack trace after a halt is not as useful as the same code
compiled with MSVC++4.2 and using the older version of windbg. The newer
setup never has the calls made to routines inside my driver except
DriverEntry(). The old setup, using the exact same source contains a much
better and useful stack trace.

Chuck R.

2

Is there any difference between the current windbg & the old one when
using the same compiler?

-----Original Message-----
From: Chuck R [mailto:xxxxx@usa.net]
Sent: Friday, July 21, 2000 8:52 AM
To: Kernel Debugging Interest List
Subject: [windbg] MSVC++ 6.0 windbg

I’m having strange problems with the newer windbg that works with MSVC++
6.0
in that the stack trace after a halt is not as useful as the same code
compiled with MSVC++4.2 and using the older version of windbg. The
newer
setup never has the calls made to routines inside my driver except
DriverEntry(). The old setup, using the exact same source contains a
much
better and useful stack trace.

Chuck R.

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

The new WinDbg works best with PDB files.

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Friday, July 21, 2000 10:16 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: MSVC++ 6.0 windbg

Is there any difference between the current windbg & the old one when using
the same compiler?

-----Original Message-----
From: Chuck R [mailto:xxxxx@usa.net mailto:xxxxx]
Sent: Friday, July 21, 2000 8:52 AM
To: Kernel Debugging Interest List
Subject: [windbg] MSVC++ 6.0 windbg

I’m having strange problems with the newer windbg that works with MSVC++ 6.0

in that the stack trace after a halt is not as useful as the same code
compiled with MSVC++4.2 and using the older version of windbg. The newer
setup never has the calls made to routines inside my driver except
DriverEntry(). The old setup, using the exact same source contains a much
better and useful stack trace.

Chuck R.

—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)</mailto:xxxxx>