Faulting thread stack-trace using IDebugControl::GetStackTrace

Question

I have a minidump of crashed application and I would like to analyse it using DbgEng in my own library. Does anyone now how can I get the stacktrace of the thread that caused the program crash using IDebugControl::GetStackTrace?

I appreciate any kind of help

Thx

OK, I have a solution now. The solution is described in this article http://blogs.msdn.com/b/joshpoley/archive/2008/11/10/minidumps-and-bad-stacks.aspx — runnydead, Oct 11 '11 at 13:09

score 1 · Accepted Answer · edited Jan 08 '15 at 22:33

1

Depending on how the crash dump was generated, it might be using embedded contexts. Use the IDebugControl4 interface which gives you access to the GetStoredEventInformation and GetContextStackTrace methods. If GetStoredEventInformation fails, you can fall back on the GetStackTrace method.

The solution is described in this article http://blogs.msdn.com/b/joshpoley/archive/2008/11/10/minidumps-and-bad-stacks.aspx

edited Jan 08 '15 at 22:33

PAT

507
5
13

answered Oct 12 '11 at 07:47

runnydead

618
1
7
17

The link is dead. – Etienne de Martel Jul 27 '22 at 17:48

Faulting thread stack-trace using IDebugControl::GetStackTrace

1 Answers1