When the correct symbols are installed, the call stack shown in the Drwtsn32.log file appears as follows:
000ae444 018e2954 01ff24fc 00000146 000ae4d0 nNOTES!OSAllocDBlock+0xb9 000ae458 018e25f8 01ff24fc 00000146 000ae4d0 nNOTES!OSAllocDBlock+0x14 000ae498 018e7ee7 02038fe0 00000146 000ae4cc nNOTES!OSBBlockAddr+0x1d8 000ae4bc 018e7d4b 02038fe0 02099080 02e102cc nNOTES!OSMemRealloc+0x217 000ae4e8 09201868 02099080 00000100 00000006 nNOTES!OSMemRealloc+0x7b 000ae568 01cc8d98 037feef8 00000095 00000026 NXRTF!FirstPass+0x368 000ae5ac 09201292 00fffffc 09201500 00000000 nNOTES!EnumCompositeFD+0x188 000ae72c 09202692 000ae738 445c3a43 4d55434f NXRTF!CD2RTF+0x262 000ae944 092025ca 000aeb8c 0914cfc8 00000000 NXRTF!ExportRTF+0x112 000aeb5c 022654f5 000aeb8c 00000003 00000000 NXRTF!ExportRTF+0x4a 000aee78 02257b66 02241550 091b8ff0 0000000a LSNTSHC!NTSHCMessage::ExportNotesCompositeData+0x105 000af12c 018a641e 00000000 000af28c 59010261 LSNTSHC!NTSHCMessage::getBodyRTF+0x276 000af2bc 100a0aa4 000af388 000af390 00000000 mlmignts!INEGetNextMessage+0x5be 000af3a0 1002dfc2 0141af90 01416ff0 00008001 mlmig32!CNotesExtract::IGetUserMail+0x494 000af7c8 10015a20 000af7ec 016cafb8 c0000000 mlmig32!CNotesMigProcess::Execute+0xa62 000af7f4 77e11d0a 00220346 00008001 00000000 mlmig32!ProgressDlg+0x270 000af814 77e22b0d 100157b0 00220346 00008001 USER32!UserCallWinProc+0x18 000af850 77e22722 00220346 00008001 00000000 USER32!DefDlgProcWorker+0xbf 000af868 77e11d0a 00220346 00008001 00000000 USER32!DefDlgProcA+0x21 000af888 77e11bc8 77e22701 00220346 00008001 USER32!UserCallWinProc+0x18