!wstack dumps not all stack objects like !dso

[rodneyviana]

!wstack dumps not all stack objects like !dso

[rodneyviana]

Hi Alois-xx, Do you mean show repeats? !wstack traverses the full stack, covering even more range than !sos.dso. Do you have a particular repro you can share? Thanks, Rodney Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Alois-xx <[email protected]> Sent: Sunday, January 20, 2019 10:21 AM To: rodneyviana/netext Cc: Subscribed Subject: [rodneyviana/netext] !wstack dumps not all stack objects like !dso (#5) I love the !wstack command but for some cases where I am searching for stale references of already left methods I sometimes want to see if some hints of already left methods are on the stack. The !dso command travereses the full stack but !wstack only the valid one. Could you add to !wstack e.g. a -full option to list all managed references? By the way your Windbg extension is by far the best out there for managed code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frodneyviana%2Fnetext%2Fissues%2F5&data=02%7C01%7C%7Cf33bbbc2f25a43060f2d08d67ef362e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636835981125990162&sdata=5oBxaw2d5G64VCz74iL%2BJ7MhbYLO0j1ZWC7D288NEmo%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAafWAsrMb-x_XMqizHcCw0S3iOLJesZbks5vFJefgaJpZM4aJuKr&data=02%7C01%7C%7Cf33bbbc2f25a43060f2d08d67ef362e7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636835981125990162&sdata=uC1EVaKcfBYulvE347v1vNFhkf%2FIZR4R7NGA1eDGiyc%3D&reserved=0>.

[Alois-xx]

I will check with a specific dump. I have seen that !wstack returned no objects but !dso did return some objects of a threadpool thread which was waiting for more work wich was before that juggling around some Window objects which did cause some deadlock. With !wstack I did not get any objects back. It looks like !wstack is looking only at the stack from top to the currently executing method but not below of "older" methods which are no longer on the stack.

[rodneyviana]

Hi Alois-xx, NetExt uses all entries in the thread stack. The range can be verified by using dt _TEB @$teb or simply !teb Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Alois-xx <[email protected]> Sent: Sunday, January 20, 2019 3:16 PM To: rodneyviana/netext Cc: Rodney Viana; Comment Subject: Re: [rodneyviana/netext] !wstack dumps not all stack objects like !dso (#5) I will check with a specific dump. I have seen that !wstack returned no objects but !dso did return some objects of a threadpool thread which was waiting for more work wich was before that juggling around some Window objects which did cause some deadlock. With !wstack I did not get any objects back. It looks like !wstack is looking only at the stack from top to the currently executing method but not below of "older" methods which are no longer on the stack. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frodneyviana%2Fnetext%2Fissues%2F5%23issuecomment-455903202&data=02%7C01%7C%7C7003f16a28e74c733e6d08d67f1c99e5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636836158142148302&sdata=hYUFkozEokJTGVw6IE4qDO4Rf%2BWS4IkMWMGQApoOnPQ%3D&reserved=0>, or mute the thread<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAafWAuC4iVStg9tTv8wc-6Qy568QVlPMks5vFNzEgaJpZM4aJuKr&data=02%7C01%7C%7C7003f16a28e74c733e6d08d67f1c99e5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636836158142148302&sdata=B0YTPLkVZ2BSNyeBDdf66Z%2B6z9Y3RrlYbvF8SnnfHsY%3D&reserved=0>.

[Alois-xx]

I did look at an older dump. You are right !wstack is indeed returning more objects. It is !dso which is showing less objects. I was just looking around for updates of netext and remembered that issue wrong.