Hi -
I’m using Redemption as an OLEObject to access a mailbox in Outlook on Windows.
On some machines, for some accounts, doing so gives me a hard crash (‘The application has stopped responding and needs to close’.)
Looking at the CrashDump which Windows has output, I’ve got this:
–
PROCESS_NAME: Light Blue.exe
ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.
FAULTING_MODULE: 74b60000 kernel32
DEBUG_FLR_IMAGE_TIMESTAMP: 511ab2ea
MODULE_NAME: MSPST32
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 147f203c
READ_ADDRESS: 147f203c
FOLLOWUP_IP:
MSPST32+213e6
64ba13e6 f7412c00000080 test dword ptr [ecx+2Ch],80000000h
MOD_LIST:
FAULTING_THREAD: 0000193c
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_WRONG_SYMBOLS
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
DEFAULT_BUCKET_ID: INVALID_POINTER_READ
LAST_CONTROL_TRANSFER: from 64ba1372 to 64ba13e6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0020ea04 64ba1372 29cc2b28 29cc07d0 29cc2b28 MSPST32+0x213e6
0020ea28 64c7ca22 00000001 10b152e8 10ae07d0 MSPST32+0x21372
0020ea40 66768ee5 29cc2b28 00000000 00000000 MSPST32+0xfca22
0020ea78 66768b8d 66723650 00000000 0020ea90 OLMAPI32+0x68ee5
0020ea88 66723661 0020eabc 767d62fa 000c1488 OLMAPI32+0x68b8d
0020ea90 767d62fa 000c1488 000005b1 00000000 OLMAPI32+0x23661
0020eabc 767d6d3a 66723650 000c1488 000005b1 user32+0x162fa
0020eb34 767d77c4 16f92364 66723650 000c1488 user32+0x16d3a
0020eb94 767d788a 66723650 00000000 0020ebd8 user32+0x177c4
0020eba4 6e224ee6 0020ebbc 074da530 000003be user32+0x1788a
0020ebd8 02d59138 0020ebe0 6e224dc0 02dff2e3 RBGUIFramework+0xc4ee6
0020ebf4 02dff341 070c3cc0 070c3cc0 070c3cc0 0x2d59138
0020ec94 6e225048 0749cb00 6e224dc0 013b0000 0x2dff341
0020ecac 6e22506a 003fed08 6e2236ee 02f8b013 RBGUIFramework+0xc5048
0020ece8 02d267da 0020ecf0 4d885d8e 073cb390 RBGUIFramework+0xc506a
0020ed44 02d20024 0020ed4c 0020ed94 6e1b4a3a 0x2d267da
0020ed50 6e1b4a3a 0000ed08 ed68ed94 71840000 0x2d20024
0020ed94 013b1312 013b0000 00000000 00532fab RBGUIFramework+0x54a3a
0020f9d4 013b1641 013b0000 00000000 00532fab Light_Blue+0x1312
0020fa64 74b7336a fffde000 0020fab0 77049f72 Light_Blue+0x1641
0020fa70 77049f72 fffde000 772f0881 00000000 kernel32+0x1336a
0020fab0 77049f45 013b1694 fffde000 00000000 ntdll+0x39f72
0020fac8 00000000 013b1694 fffde000 00000000 ntdll+0x39f45
–
Debugging this sort of thing is something I’ve never done before; can anyone give me any clues as to where to start?
Thanks,
Hamish