Open AntonKukoba1 opened 1 year ago
This is the first I've seen this problem. Do you have steps to reproduce?
Hello Jason,
No, I just installed Windbg preview, then I was suggested to upgrade to "release version" of Windbg. And as soon as I tried to use it to debug the app, I noticed that the call site column was gone. Nevertheless I can give some details. Today I've noticed that the column is not fully gone, it's resized to 0 width. So you can recover it by dragging the rest of the columns. Yet it's very frustrating when you see it.
пн, 25 вер. 2023 р. о 19:26 Jason Shirk @.***> пише:
This is the first I've seen this problem. Do you have steps to reproduce?
— Reply to this email directly, view it on GitHub https://github.com/microsoftfeedback/WinDbg-Feedback/issues/124#issuecomment-1734086267, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIM3VPQ2JJO2NHW6WUR7AKLX4GWDTANCNFSM6AAAAAA5BDEWLI . You are receiving this because you authored the thread.Message ID: @.***>
The same problem for me. Broken with update to release. Old beta versions worked like a charm.
The call stack window doesn't show the call site column, despite it's enabled. So it shows just pointers of Child SP. Nevertheless if you use k command to print the call stack, the names are printed just fine.