Bug 24180 – Debugger no longer shows locals "busy" VS2022

Status
NEW
Severity
regression
Priority
P1
Component
visuald
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2023-10-08T02:49:13Z
Last change time
2023-10-18T20:22:39Z
Assigned to
No Owner
Creator
Richard Cattermole
Moved to GitHub: visuald#261 →

Attachments

IDFilenameSummaryContent-TypeSize
1892Capture.PNG"Busy" locals window screenshotimage/png8127

Comments

Comment #0 by alphaglosined — 2023-10-08T02:49:13Z
Created attachment 1892 "Busy" locals window screenshot I first experienced this around a year ago. At the time I assumed it was to do with shared library support + -betterC, however as time has gone on and more people reported it, it does not appear to be related. Typically when ending of debugging (regardless of reason), it tends to take a long time as well to finish stopping. As of this writing, I have gotten around to trying to determine the cause of this problem and have been able to determine it is related to the VisualD plugin. With it disabled it no longer has these issues. Originally I had 1.3.1 and then updated to the 1.4.0-beta1, as well as updated VS 2022, to latest patch, hoping that it would work. These problems exhibit for both ldc and dmd for all versions I have tried during this time period. I've included a screenshot of the "busy" (the busy text isn't there, but everything else matches) locals window. I have attempted to remove debug info for both CV4 & CV8 to try and see if that affects it. I used the pdbutil from LLVM to dump the pdb file, and compared it against a comparable pdb file produced from clang-cl. However it looks ok. Funky, but nothing explicitly wrong with what it is generating. This aligns with a report that remedybg does show locals ok.
Comment #1 by robert.schadek — 2023-10-18T20:22:39Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/visuald/issues/261 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB