Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

MSVC++ 6.0 windbg

OSR_Community_UserOSR_Community_User Member Posts: 110,217
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.

Comments

  • OSR_Community_User-48OSR_Community_User-48 Member Posts: 74
    Is there any difference between the current windbg & the old one when
    using the same compiler?

    -----Original Message-----
    From: Chuck R [mailto:[email protected]]
    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: [email protected]
    To unsubscribe send a blank email to $subst('Email.Unsub')
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    The new WinDbg works best with PDB files.

    -----Original Message-----
    From: Nathan Nesbit [mailto:[email protected]]
    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:[email protected] ]
    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: [email protected]
    To unsubscribe send a blank email to $subst('Email.Unsub')
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE