1,853 questions
Lost debug cursor when debugging drivers in Visual Studio 2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 9%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Doctal
6
Reputation points
Debug cursor missing in source code when debugging drivers (yellow arrow). When debugging a normal console application, the cursor is present. I was informed that this might be related to Windbg.
Windows for business | Windows Client for IT Pros | Devices and deployment | Other
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 23%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
Dylan Barrie 0 Reputation points2023-05-15T17:46:12.34+00:00 I am having the same issue, but with Visual Studio 2019. Note that if I use the "Show Next Statement" command, the text caret does move to the correct location. The debugger is well aware of where the instruction pointer is, but it looks like whatever is meant to draw that debug cursor is just not doing so.
Sign in to comment
Sign in to answer