Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
MSVC++ 6.0 windbg
OSR_Community_User
Member Posts: 110,217
in 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.
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.
Howdy, Stranger!
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
| Internals & Software Drivers | 19-23 June 2023 | Live, Online |
| Writing WDF Drivers | 10-14 July 2023 | Live, Online |
| Kernel Debugging | 16-20 October 2023 | Live, Online |
| Developing Minifilters | 13-17 November 2023 | Live, Online |
Comments
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')
-----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')