How to trace call stack

Question

2.33/5 (3 votes)

See more:

I saw a simple calling stack on Turbo C 3.0

But I am wandering for a that simple calling stack. I am working on a multi-threading application and I am having a error in the query, so when I run it stuck in certain function. then I want to see the bad boy who called that individual function with improper query. I know if i debug carefully i will find that individual function. but i want to see it on the calling stack, someone guide me :)

p.s.: The question can be shorter than this, but I could not make it. :(

Posted 30-May-12 16:55pm

Mohibur Rashid

Updated 30-May-12 17:45pm

v2

Add a Solution

2 solutions

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)

Aescleal · Answer 1 · 2012-05-30T21:39:00

While this won't help if it's a timing issue you could log who's making the call and what the parameters are. If you flush the log before each call you know who's making the crap call AND what the parameters are. If you wrap the lot up in a macro it shouldn't be too hard to instrument your code this way (I know, I don't have to do it... :-) ).

If more than one thread calls the offending item then you'll have to create a log for each thread but hopefully it's just one thread messing up.

Another option would be to wrap your offending function in another one that does parameter validation and calls DebugBreak when something dodgy is passed. Then if you run it under a debugger it'll break when it gets the dodgy data, you can examine the call stack, find the offending caller AND see what its state is at the time.

Edit: Dodgy English Alert!!

Pablo Aliskevicius · Answer 2 · 2012-05-30T20:27:00

Solution 1

See http://win32.mvps.org/misc/stackwalk.html[^]
Also http://www.cygnus-software.com/papers/release_debugging.html[^]
You may want to ship a .pdb file for each .dll.

The articles refer to VC6, but the Windows API is still there.

Hope this helps,

Pablo.

Posted 30-May-12 20:27pm

Pablo Aliskevicius

Updated 30-May-12 21:43pm

v2