General discussion

Locked

how to use this error for diagnosis?

By DerekC ·
The following Windows error message has lots of detail, but I have no idea
how to use it for diagnostic purposes. Can anyone suggest something? (The
crash occurs when using one particular form in a VB application we are
building. The form usestwo 3rd party controls: Infragistics' DataTable
8.0 and DevComponents' MDIExtender.)

***********************************
CASEMANAGEMENT caused an invalid page fault in
module <unknown> at 0000:03e37555.
Registers:
EAX=00000f6f CS=0187 EIP=03e37555 EFLGS=00010246
EBX=0064f6b2 SS=018f ESP=0064f65c EBP=0064f698
ECX=d18fa510 DS=018f ESI=0064f6e6 FS=620f
EDX=00014d24 ES=018f EDI=00000000 GS=0000
Bytes at CS:EIP:

Stack dump:
bff72317 00000000 00000000 0064f6ba 86b649cf 414d49cf f81416ff 00040064
04040000 08900000 08900000 0064fbec bff7186d 00000f6f 00000000 0064f6ec

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

how to use this error for diagnosis?

by Peter Ritchie In reply to how to use this error for ...

Essentially you can use that information to figure out roughly were in the binary the error occured. This can be done by finding out where in the source code the offset occurs. This can easily be done with MAP files. I don't know if VB will generate map files--but you might be able to get by with DR. Watson and DBG files.

check out http://support.microsoft.com/support/kb/articles/Q133/1/74.asp and http://support.microsoft.com/support/kb/articles/Q258/2/05.asp

Collapse -

how to use this error for diagnosis?

by DerekC In reply to how to use this error for ...

Unfortunately these suggestions all apply to other platforms. VB doesn't generate MAP files. Dr. Watson gives a little bit more information -- "The application or one of its DLLs used an uninitialized function pointer variable or attempted to use a DLL which has already been freed." -- but that doesn't point toward the problem in the source code. The Microsoft articles seem to all be talking about C++ stuff or else using CodeView, which apparently is from Windows 3.1

Collapse -

how to use this error for diagnosis?

by kschang In reply to how to use this error for ...

Merely a suggestion...

There may not be an answer to your satisfaction on this topic. Invalid Page fault is basically a program accessing a region that was earmarked for another program, and it may NOT be your program that's doing it! (Could be one of those ActiveX, or random interaction between your stuff and installed stuff, and so on)

The only "real" way to track this down is to step through your code line by line with a debugger and find the instruction it chokes on, and trace that back to the source code. VB can't do quite do that. Remember, you don't really allocate memory in VB (except DIM, but that's another story), so any memory allocation problem is either VB's fault or the component's fault.

While the message appears tohave a lot of information, it's merely a snapshot of what's in the CPU at the exact time of error. Without knowing where your program loaded to and such, it's NOT useful at all!

You may be able to work AROUND it by narrowing down the specific component or module that is causing the error. Have you tried using some other similar ActiveX components from a different vendor? Get the latest service packs and such?

Collapse -

how to use this error for diagnosis?

by DerekC In reply to how to use this error for ...

Actually, that's the direction we've ended up going in. We changed the way the code accesses one of the properties on MDIExtender, and it has reduced (though not entirely eliminated) the crashes. Also, we got a debugging package from Mutek called Bugtrapper, and hope that it will help find the bug when it does occur.

Collapse -

how to use this error for diagnosis?

by DerekC In reply to how to use this error for ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums