{"id":5902,"date":"2013-03-27T13:57:57","date_gmt":"2013-03-27T21:57:57","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=5902"},"modified":"2013-03-28T09:22:32","modified_gmt":"2013-03-28T17:22:32","slug":"another-powershell-v3-breakpoint-bug","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2013\/03\/27\/another-powershell-v3-breakpoint-bug\/","title":{"rendered":"Another PowerShell V3 breakpoint bug [UPDATED]"},"content":{"rendered":"

[UPDATE] Some users report that they cannot reproduce this behavior on Windows 8. Our Windows 8 machines show the same behavior. We will investigate further what the differences are.<\/p>\n

\"DisabledBreakpoint\"<\/a> <\/p>\n

[END UPDATE]<\/p>\n

As we previously reported here (PowerShell V3 breakpoint bug<\/a>) PowerShell V3 has a serious breakpoint bug where breakpoints cannot be set or removed after a script has been started.<\/p>\n

Our team has now discovered yet another breakpoint related bug in V3, which basically renders Disable-PSBreakpoint inoperative. It just doesn\u2019t work. Let me illustrate with the Microsoft Powershell V3 ISE under Windows 7 SP1.<\/p>\n

We open a simple four line script.<\/p>\n

\"SNAGHTML794f905\"<\/a><\/p>\n

Yes, it has Write-Host in it, it doesn\u2019t matter. I set a breakpoint at line 15, as indicated by the coloring. Now we go and disable the breakpoints using this:<\/p>\n

\"image\"<\/a> <\/p>\n<\/p>\n

As you can see here, the ISE stops at the disabled breakpoint.<\/p>\n

\"SNAGHTML7983fd5\"<\/a><\/p>\n

Well, it could be that it\u2019s just the ISE that has a bug, so lets try another way. After closing the ISE, restarting it and loading the file again, we do this:<\/p>\n

\"SNAGHTML79c06bb\"<\/a><\/p>\n

This time we use cmdlets to set and disable the breakpoint. The coloring in the file shown above changes accordingly as you execute the cmdlets.<\/p>\n

Now start the script:<\/p>\n

\"SNAGHTML79d58e0\"<\/a><\/p>\n

Once again, PowerShell V3 stops at the disabled breakpoint. Using the V2 engine this does not happen and disable-psbreakpoint works as expected.<\/p>\n","protected":false},"excerpt":{"rendered":"

[UPDATE] Some users report that they cannot reproduce this behavior on Windows 8. Our Windows 8 machines show the same behavior. We will investigate further what the differences are. [END UPDATE] As we previously reported here (PowerShell V3 breakpoint bug) PowerShell V3 has a serious breakpoint bug where breakpoints cannot be set or removed after […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[25],"tags":[754,757,819,28,818,756],"class_list":["post-5902","post","type-post","status-publish","format-standard","hentry","category-windows-powershell","tag-breakpoint","tag-bug","tag-disable-psbreakpoint","tag-powershell","tag-set-psbreakpoint","tag-v3"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t