You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for sharing your wonderful StackWalker library! I encountered an issue which I am not sure if it is a bug. Can you kindly take a look into it?
I downloaded the code from the master branch and used the latest VS2019 to build. When I derived my MyStackWalker class like shown in the README
But I wish to write the callstack into my log and have my customer send it back to me. I have no access to customer machine and cannot possibly ask him/her to debug on my behalf.
Please kindly advise.
Thank you in advance.
Update: I cannot reproduce this problem on my home PC with VS2022.
Update again: It happens on my home PC with VS2022. Looks like it is an intermittent problem.
The text was updated successfully, but these errors were encountered:
Thank you for sharing your wonderful
StackWalker
library! I encountered an issue which I am not sure if it is a bug. Can you kindly take a look into it?I downloaded the code from the master branch and used the latest VS2019 to build. When I derived my
MyStackWalker
class like shown in the READMEAnd I called it this way.
Only 1 line of callstack is shown on my commandline console.
And the
ShowCallstack()
returns from the if condition at line 1342 ofhttps://github.com/JochenKalmbach/StackWalker/blob/master/Main/StackWalker/StackWalker.cpp#L1342
But when I use the original StackWalker class like this,
I can see all the callstack in Sysinternal's DebugView.
But I wish to write the callstack into my log and have my customer send it back to me. I have no access to customer machine and cannot possibly ask him/her to debug on my behalf.
Please kindly advise.
Thank you in advance.
Update: I cannot reproduce this problem on my home PC with VS2022.
Update again: It happens on my home PC with VS2022. Looks like it is an intermittent problem.
The text was updated successfully, but these errors were encountered: