First I tried to reproduce the bug in another solution but I could not, sorry about that.
However, in a project I'm working on, I can perfectly reproduce the problem 100% of times.
The way to reproduce is as follow:
1. Set two breakpoints in the code, where one can be hit and the other cannot be hit.
* the icon is a thin red circle filled in white, with a little yellow triangle warning mark (see line 19 of attached image)
* this can be verified only at runtime
2. Run the app and wait until the reachable breakpoint hits.
3. Remove the unreachable breakpoint either by clicking it with the mouse or pressing F9.
4. Press F5 to continue.
At this point, my Visual Studio crashes.
There are no error message of any kind any where. Just the Node command windows displaying 'Error 10054' a bit after, but I guess this is just the 'connection reset by peer' socket error code.
Where I can set the unreachable breakpoint is in an anonymous function passed to a function call as parameter.
My environment:
* Windows 8.1
* Visual Studio Express 2013 for Web
* Nodejs 0.10.26
* Nodes.js Tools for Visual Studio 1.0 Beta (dated of 2014/04/04)
I hope that could help.
However, in a project I'm working on, I can perfectly reproduce the problem 100% of times.
The way to reproduce is as follow:
1. Set two breakpoints in the code, where one can be hit and the other cannot be hit.
* the icon is a thin red circle filled in white, with a little yellow triangle warning mark (see line 19 of attached image)
* this can be verified only at runtime
2. Run the app and wait until the reachable breakpoint hits.
3. Remove the unreachable breakpoint either by clicking it with the mouse or pressing F9.
4. Press F5 to continue.
At this point, my Visual Studio crashes.
There are no error message of any kind any where. Just the Node command windows displaying 'Error 10054' a bit after, but I guess this is just the 'connection reset by peer' socket error code.
Where I can set the unreachable breakpoint is in an anonymous function passed to a function call as parameter.
My environment:
* Windows 8.1
* Visual Studio Express 2013 for Web
* Nodejs 0.10.26
* Nodes.js Tools for Visual Studio 1.0 Beta (dated of 2014/04/04)
I hope that could help.