stack trace is too simple

[icepng]

And I test in IE, when crashed my IE, and I wanted to get the stacktrace by crash.fullReport(), but the info is too simple, not the deep 16.

Stack trace:
Frame            Origin
0000007647653960 000000000000007E (0x7e)

Can I get the stack trace like k in windbg by setting something in winappdbg? thx.

[MarioVilas]

There could be any number of reasons why the stack trace looks like that, for example stack buffer overflows tend to corrupt the stack trace. This is unavoidable, I'm afraid.