1

Topic: [To convergence] VS2013 (With ++). Break points and brakes

Simply to convergence by that who, as well as I, can, faces it for the first time. Not to waste in vain time and nerves. In general, it appears, presence of points of interruption even in a case when they do not get to a control flow by debugger operation, can is all the same considerable decelerate program operation under debugging (at me it is time in 5-8). Moreover and to be shown by embarkations . Therefore, , it is necessary to get rid from unnecessary  at once, instead of to wait for a suitable case.

2

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, _hum _, you wrote: __> in general, it appears, presence of points of interruption... All the same can decelerate considerably program operation under debugging It is necessary to specify that pluses Because with  the same was just to VS 2013. Well, now it is at least clear as C# team got rid of this problem.

3

Re: [To convergence] VS2013 (With ++). Break points and brakes

And  examples for playback of such behavior will be? What  take off, whence? Can to you it is necessary to make a post in a connection?

4

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, VTT, you wrote: VTT> And  examples for playback of such behavior will be? There is no it happens in the initial big project, and to search and build playing back simple example is not present either time, or desire. VTT> what  take off, whence? The pattern was such: fulfilled , saw wild brakes, decided to spit and push f5 (instead of f10) - execution reflected, and then took off  type something there in bla-habdler-ole.dll

5

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, Sinix, you wrote: S> Hello, _hum _, you wrote: __>> in general, it appears, presence of points of interruption... All the same can decelerate considerably program operation under debugging S> It is necessary to specify that pluses Because with  the same was just to VS 2013. S> Well, now it is at least clear as C# team got rid of this problem. And they got rid?

6

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, _hum _, you wrote: __> and they got rid? If to understand to get rid as "transfer to another" it is certain yes Since VS 2013 brakes at managed-code debugging definitely less.

7

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello,  _hum _, you wrote: VTT>> And  examples for playback of such behavior will be? __> there is no it happens in the initial big project, and to search and build playing back simple example is not present either time, or desire. Working with the big project on a C ++ (MFC) under MSVS-2013 anything similar did not note. Thus, operation with the project from 5 exe-modules and the order 25 dll-modules took place. VTT>> what  take off, whence? __> the pattern was such: fulfilled , saw wild brakes, decided to spit and push f5 (instead of f10) - execution reflected, and then took off  type something there in bla-habdler-ole.dll If it is possible,  _hum _, at least there are more than particulars on given your situation. Quite probably, it is a singularity of your project, thus the reason - not in the studio, and in any not absolutely correct decisions (yours, or authors of the project - your colleagues).

8

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, AlexGin, you wrote: AG> Hello,  _hum _, you wrote: VTT>>> What  take off, whence? __>> the pattern was such: fulfilled , saw wild brakes, decided to spit and push f5 (instead of f10) - execution reflected, and then took off  type something there in bla-habdler-ole.dll AG> If it is possible,  _hum _, at least there are more than particulars on given your situation. AG> it is quite possible, it is a singularity of your project, thus the reason - not in the studio, and in any not absolutely correct decisions AG> (yours, or authors of the project - your colleagues). Well, I do not insist. Simply "take into consideration" (if the beginning strongly to brake try to delete unnecessary ) by the way, like clear, why so can be - because breaks interpose the code which can be not optimal on speed of performance (especially conditional) and to brake all process.

9

Re: [To convergence] VS2013 (With ++). Break points and brakes

Hello, _hum _, you wrote: __> it is simple to convergence by that who, as well as I, can, faces it for the first time. Not to waste in vain time and nerves. __> in general, it appears, presence of points of interruption even in a case when they do not get to a control flow by debugger operation, can is all the same considerable decelerate program operation under debugging (at me it is time in 5-8). Moreover and to be shown by embarkations . Therefore, , it is necessary to get rid from unnecessary  at once, instead of to wait for a suitable case. At me generally the studio stablly falls, if 2  at once I debug about 3 Years ago when  were less, did not fall. And brakes was not very much. On small projects - flies.