Visual Studio는 중단 점을 잊지 않습니까?

Visual Studio는 중단 점을 잊지 않습니까?

---

Visual Studio는 이전 디버깅 세션의 중단 점을 기억합니다.

그러나 디버깅 할 때 이러한 "이전"중단 점 중 하나를 클릭하면 지워집니다. 일시적으로 만 삭제됩니다. 내가 의미하는 바는 다음에 디버깅 할 때 제거했다고 생각한 중단 점이 다시 있다는 것입니다.

이것은 매우 성가신 일입니다. 그렇게하지 않는 설정이 있습니까?

---

Debug다음 메뉴로 이동Delete All Breakpoints Ctrl+Shift+F9

---

문제는 중단 점의 하위 중단 점이 지속된다는 것입니다. 디버그 세션 중 중단 점을 설정할 때 하위 중단 점이 작성됩니다 (특정 상황에서).

중단 점 (및 하위)을 삭제하는 확실한 방법은 중단 점 창에서 수동으로 중단 점을 찾아 삭제하는 것입니다. (항목의 최상위 노드를 선택하고를 누르십시오 Delete.)

VBScript 매크로를 지원하는 이전 버전의 Visual Studio를 실행중인 경우 여기에 게시 된 (디버그 세션간에) 매크로를 실행하여 하위 중단 점을 제거 할 수 있습니다. 이렇게하면 글리프를 좀 더 효과적이고 예측 가능하게 클릭하여 중단 점을 제거 할 수 있지만 계속 문제가되고 어색합니다.

---

'BreakPoints Window'를 찾는 데 어려움을 겪고 있었으므로 여기를 여는 빠른 방법이 있습니다. ctrl+ alt+B

---

또는 수동으로 'Debug-> Windows-> Breakpoints'로 이동하여 열 수 있습니다.

---

또는 ctrl+ shift+ F9를 눌러 한 번에 모든 중단 점을 삭제할 수 있습니다 !

---

여기에 몇 가지 대답이 있지만, 제 생각에는 디버깅 중에 사용하는 행동이 산만합니다 (내 초점을 잃고 싶지 않습니다).

My flow with sticky breakpoints during breakpoints is as follows:

During debug, DISABLE the breakpoint instead of removing it.

Possible ways of disabling a breakpoint:

• hover with cursor and click the two cycle icon;
• or use context menu on it;
• or keyboard short-cut CTRL+F9 (not Shift+CTRL+F9, as it clears all breakpoints).

Later on, during development, I remove a disabled breakpoint when I see one.

PS. It's also a good practice to remove all breakpoints once in a while.

---

• Start your debug session with a minimal number of files open, as you debug the unwanted breakpoints will show up and the containing files will open in new tabs.
• Terminate the debug session and open the breakpoints window (from the debug toolbar, for some reason it is not in the view menu).
• For each file, enter the name of the file in the search area of the breakpoints window and press enter to filter out the breakpoints by file.
• You can then click on each breakpoint in the window to see where they are located in the code and delete them if you want. A bit tedious but that the best way I found to get rid of those unwanted ghost breakpoints... Bookmarks and breakpoints management.. Those functions were probably last enhanced sometime during the last century...

---

Most breakpoints can be removed during debug-session, but some are stuck (probably a bug in Visual Studio).

It you want to remove only the breakpoint which is stuck, then use the "Breakpoints" windows found on the debug menu. There you will probably see that your breakpoint exist multiple times for the same row. Simply rightclick and delete it.

---

A quick alternative answer to this old question that just hit me with Visual Studio 2017.

If possible, just cut and paste the code with the breakpoint on it. The breakpoint goes away with the cut.

---

Go to debug > windows > breakpoints and find breakpoints and remove those from pane.

as It was answered here

---

I consider this a design flaw, its very frustrating and something we have had to live with for a long time. We hit it so often that it just becomes the norm. The solutions given so far are really work around.

A better solution would be to get together and vote for a change on the Visual Studio User Voice. It seems like this has been logged a few times so we should pick one to vote up.

https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/31123351-delete-disable-break-point-while-debugging-should

참고 URL : https://stackoverflow.com/questions/5983918/visual-studio-refuses-to-forget-breakpoints