This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 46%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Folks:
Developing on Windows 10 Pro, Visual Studio Community 2022, all C++, no MFC.
I'd like to log and/or display a call stack, line numbers, function names, whatever hints are available, when a commonly used function is called.
A break point won't do because this function is going to be called many times from many points in the application and I won't know if there's something interesting to look at until I've run the code.
I'm looking for finding this information for both debug and release code.
I'm assuming less, or perhaps no, stack information is available for a release build, but I'd like testing to be done by users who won't have the development environment.
Perhaps there's a way to add some debugging information to a release build I could give the beta testers, but not put in the "real" release build the customers will see.
Thanks
Larry
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
Perhaps there's a way to add some debugging information to a release build I could give the beta testers, but not put in the "real" release build the customers will see.
You can generate debugging information and a pdb for release builds. Of course, optimization in release builds makes debugging them more difficult. And optimizations may obscure what you are hoping to see in a call stack.
Answer accepted by question author
First of all you want to make sure that you have symbols for Windows dlls as well as for your own application. Of course, debuggers are capable of displaying a call stack. If your interest is to generate a call stack display programmatically then the stackwalk function looks promising.
@a_unique_name There is also https://www.codeproject.com/articles/11132/walking-the-callstack-2. I haven't tested this article's code. And more recent code from the author of the article https://github.com/JochenKalmbach/StackWalker
Thanks again RLWA32, for the 1000th time:
I was able to find the guilty code before I tried this.
I'll look into this debug feature when I have time.
As always, I appreciate your advice.
Larry