Re: CIPE-Win32 (2.0-pre7) BSOD|
"Damion K. Wilson" <dkw,AT,rcm,DOT,bm>|
Thu, 5 Apr 2001 21:39:41 +0200|
Yeah, but I (currently) don't know how to symbolically deconstruct a .sys
file. It shouldn't be hard, though (!). Once I can see what lives there
then I can figure out what is supposed to be working but isn't.
*********** REPLY SEPARATOR ***********
On 4/5/01 at 9:11 PM Erik Wallin wrote:
>"Damion K. Wilson" wrote:
>> Thanks, Any help at all would be appreciated. I wasn't a driver writer
>> either when I started this. Indeed, most of my more recent development
>> experience has been on Solaris and Linux than Win32.
>> If you snag a copy of WinDbg and load up the memory.dmp, you may be able
>> pinpoint where it's happening. I'm unable to force the crash on my boxes
>> I don't have one to debug.
>Sorry, but where do I find WinDbg. I have a Visual Studio Enterprise
>Win32 English. Never used it. It came with another software bundle from
>it be included there? I do have some Windows developers around that I
>for a copy if not.
>As I said, I'm not a windows developer. I would know my way around in gdb
>emacs, but not WinDbg. I'll see what I can do.
>The null pointer is accessed at offset B8, right? That could be a clue.
>we be looking for a member of a struct at offset B8.