My process is crashing in
0:000> ln 7813e7a2
(7813e725) msvcr80!_vswprintf_s_l+0x7d
(7813e7ac) msvcr80!vswprintf_s
Hi have loads of loaded DLLs, how do I find out in the dump what module called the offending print?
Asked
Active
Viewed 141 times
0
Thomas Weller
- 55,411
- 20
- 125
- 222
capsch
- 133
- 7
-
Looks like your call stack is ruined so you won't find the offending caller – YePhIcK Jul 09 '14 at 15:16
-
did you try running !analyze -v ? – Player Jul 10 '14 at 05:04
-
`ln` is for `list nearest symbols`. That's not a call stack. – Thomas Weller Jul 10 '14 at 06:04