Chris Walton wrote: > >From what I've read, it seems that the standard VS debugger can't be > used to debug kernel-mode code. Does this include user-mode code that > interfaces with KS? (such as the DirectKS stuff, which I'm using) > No. It's just like talking to any other driver. The KS interface uses DeviceIoControl to cross the border, and everything up to the border can be debugged with VS. > I have a problem where a variable in a callback is mysteriously set to > 0, _unless_ I step manually, at which point the variable is set to the > correct value and the code continues to run correctly with that value. > If I don't step (let it run), the code executes correctly on the path > it takes when that variable is 0. I've used data breakpoints in VS to > try to see if I've got some heap corruption going on, but there's none > of that. > > Is my problem related? > Nice try ;), but no. Sounds like a timing problem. -- Tim Roberts, timr@xxxxxxxxx Providenza & Boekelheide, Inc. ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/