Click here to Skip to main content
15,922,894 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
We often found below call stack, but don't know exactly where and what is the problem?

Please help me out.
Thanks in advance.



function: <nosymbols>
No prior disassembly possible
077df613 004e00 add [esi],cl
077df616 0200 add al,[eax]
077df618 d012 rcl byte ptr [edx],1
077df61a 0200 add al,[eax]
077df61c 2300 and eax,[eax]
077df61e 0000 add [eax],al
077df620 f8 clc
077df621 0d0000793c or eax,0x3c790000
077df626 98 cwde
FAULT ->077df613 004e00 add [esi],cl ds:0023:00aebcc0=55
077df616 0200 add al,[eax]
077df618 d012 rcl byte ptr [edx],1
077df61a 0200 add al,[eax]
077df61c 2300 and eax,[eax]
077df61e 0000 add [eax],al
077df620 f8 clc
077df621 0d0000793c or eax,0x3c790000
077df626 98 cwde
077df627 387a3c cmp [edx+0x3c],bh
077df62a 98 cwde

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80.DLL -
WARNING: Stack unwind information not available. Following frames may be wrong.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\USER32.dll -
ChildEBP RetAddr Args to Child
0012fc54 78202d6c 00000000 076bf628 e96e6234 0x77df613
0012fd00 782027ad 0000059f 00000000 076bf628 MFC80!Ordinal5073+0x59d
0012fd20 78201543 0000059f 00000000 076bf628 MFC80!Ordinal6275+0x22
0012fd88 78201759 00000000 000504d8 0000059f MFC80!Ordinal1028+0xa3
0012fdac 781ff883 000504d8 0000059f 00000000 MFC80!Ordinal1209+0x35
0012fdf0 7e418734 000504d8 0000059f 00000000 MFC80!Ordinal582+0x166
0012fe1c 7e418816 781ff82f 000504d8 0000059f USER32!GetDC+0x6d
0012fe84 7e4189cd 0015c1b8 781ff82f 000504d8 USER32!GetDC+0x14f
0012fee4 7e4196c7 00157850 00000001 00000000 USER32!GetWindowLongW+0x127
0012fef4 78237d12 00157850 00157850 01423908 USER32!DispatchMessageA+0xf
00000000 00000000 00000000 00000000 00000000 MFC80!Ordinal1106+0x3e

*----> Raw Stack Dump <----*
Posted

This means nothing without the source code; try using the debugger on your application to see where it crashes and then come back with some more specific details, including the line(s) of code that have a problem.
 
Share this answer
 
How are you getting this stack? are you sure this is the correct stack of the fault application?
Are you getting this stack from the memory dumped file?
 
Share this answer
 
From the looks of it, I'd say you've stomped on memory pretty good and screwed up the system utterly. There is no way anyone can help from this. If you can repro the crash, your best bet is to add some logging code to help you work out where it crashes, then tell us from there.
 
Share this answer
 
I found the bug.
Actually there is a pile up of MessageBoxs thats why it is crashing.
I think above call stack is corrupted because of that.
 
Share this answer
 
Acutally no crash happened when debugging.
And project is huge and i have no clue where it is crashing?

Is it possible from the call stack to find the steps which windows perform?
I mean to say that in MFC80 dll, what ordinal 5073 is doing after which application gets crash.
 
Share this answer
 
Actually this is what drwtsn32 has generated.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900