any idea how to use the IDiaStackWalker interaface for displaying the call stack

Question

0.00/5 (No votes)

See more:

i want to put some code in the release version of my product that prints a stack trace in the event of a crash

i'm trying to use the IDiaStackWalker interface but there seems to be no documentation that's worth a s$#t, and i can't find the required headers and libraries anyhow, i.e. Dia2.h and diaguids.lib

there is an article here http://blogs.msdn.com/b/vcblog/archive/2010/01/05/dia-based-stack-walking.aspx
which is less than useless

searching around on google it seems that no one has been able to use this interface but it looks perfect for what i need if i could only get it to work.

and ideas greatly appreciated.

thx steve

Posted 16-Jul-11 19:01pm

steveh2112

Add a Solution

2 solutions

Solution 2

cool, thanks, that helped the compile problems, now i just need to write the rest of the code

Posted 16-Jul-11 22:50pm

steveh2112

Comments

Richard MacCutchan 17-Jul-11 13:49pm

Happy to help, good luck with your project.
BTW when responding to people's posts please use the "Add Comment" link, don't add an entry as a "Solution".

steveh2112 17-Jul-11 20:07pm

ok, thanks, didn't see that. i have actually given up on writing a program to display the call stack for now, its just too hard! the example that comes with vs2010 is interested, it prints out a lot of data in the .pdf file but does not help with the stack frame, and i can't find any good documentation for the IDiaStackWalker which looks like the think i need

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Richard MacCutchan · Accepted Answer · 2011-07-16T22:10:00

Solution 1

See here[^].

Posted 16-Jul-11 22:10pm

Richard MacCutchan