A customer is running my company's program and it is stopping before it's done anywhere. They sent this information from the Windows Event Log:
Faulty module program. Exe, version 1.2.3.4, mistake address 0x00054321.
We do not have much to do, so I am trying to see as a last ditch attempt, can I know that where the disassimeter is in that condition I Run through Visual Studio, I stop it, try to see the distribution window and scroll to that address, but I get this:
00054321 ??? 00054322 ??? 00054323 ??? 00054324 ??? 00054325 ??? 00054326 ??? 00054327 ??? 00054328 ??? 00054329 ??? 0005432 A ???
Will this be because the video studio opens only part of the XES around the break or other things? It's hard for me to see how much inconvenience really is because the scrollbar does not work perfectly (I can not hold and move the scroll position, I have to scroll by line or by page.)
< P> Thanks for any insights you might have!
The mistake can also be addressed by a stack corruption problem, that is, The return address can be compromised and the wrong address has returned to 0x54321. In addition, using the technology (Java, .NET), the position between code runs can change.
Visual Studio creates a disambiguation of the entire process space. Line This means that the situation is not accessible.
You will need a stack frame to see what is going on with a core dump.
Comments
Post a Comment