October 08, 2023 [Issue 24180] New: Debugger no longer shows locals "busy" VS2022 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=24180 Issue ID: 24180 Summary: Debugger no longer shows locals "busy" VS2022 Product: D Version: D2 Hardware: All OS: Windows Status: NEW Severity: regression Priority: P1 Component: visuald Assignee: nobody@puremagic.com Reporter: alphaglosined@gmail.com Created attachment 1892 --> https://issues.dlang.org/attachment.cgi?id=1892&action=edit "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. -- |
Copyright © 1999-2021 by the D Language Foundation