![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
Debugging not working correctly
I set a breakpoint in a .NET function, and the F10 [Step Over] debug
option never reaches many of the source lines in this function. The lines that it skips are not part of a conditional expression thus should always get invoked. |
|
|||
|
RE: Debugging not working correctly
Is it possible that an exception occurs before those lines and therefore the
execution doesnt get that far? -- Ciaran O''Donnell http://wannabedeveloper.spaces.live.com "PeteOlcott" wrote: > I set a breakpoint in a .NET function, and the F10 [Step Over] debug > option never reaches many of the source lines in this function. The > lines that it skips are not part of a conditional expression thus > should always get invoked. > |
|
|||
|
Re: Debugging not working correctly
On Oct 15, 10:57*am, Ciaran O''Donnell
<CiaranODonn...@discussions.microsoft.com> wrote: > Is it possible that an exception occurs before those lines and therefore the > execution doesnt get that far? > -- > Ciaran O''Donnellhttp://wannabedeveloper.spaces.live.com > > > > "PeteOlcott" wrote: > > I set a breakpoint in a .NET function, and the F10 [Step Over] debug > > option never reaches many of the source lines in this function. The > > lines that it skips are not part of a conditional expression thus > > should always get invoked.- Hide quoted text - > > - Show quoted text - No because lines after the lines that were ignored were still reached. |
|
|||
|
Re: Debugging not working correctly
Are you absolutely sure the code that's being run (.exe and .dll's I mean,
not source code) matches your source code? "PeteOlcott" <PeteOlcott@gmail.com> wrote in message news:2a0dca19-8634-4301-92d7-cf648c1ef278@b31g2000prb.googlegroups.com... >I set a breakpoint in a .NET function, and the F10 [Step Over] debug > option never reaches many of the source lines in this function. The > lines that it skips are not part of a conditional expression thus > should always get invoked. |
|
|||
|
Re: Debugging not working correctly
On Oct 15, 11:36*am, "Adam Benson"
<Adam.Ben...@NOSPAMMYSPAM.omnibus.co.uk> wrote: > Are you absolutely sure the code that's being run (.exe and .dll's I mean, > not source code) matches your source code? > > "PeteOlcott" <PeteOlc...@gmail.com> wrote in message > > news:2a0dca19-8634-4301-92d7-cf648c1ef278@b31g2000prb.googlegroups.com... > > > > >I set a breakpoint in a .NET function, and the F10 [Step Over] debug > > option never reaches many of the source lines in this function. The > > lines that it skips are not part of a conditional expression thus > > should always get invoked.- Hide quoted text - > > - Show quoted text - Yes, it does exactly the same thing immediately after a Rebuild Solution. |
|
|||
|
Re: Debugging not working correctly
Weird. The only other thing that occurs to me is are the pdb's being
generated? And are you running the debug build? Sounds like a daft question, I know, but once or twice I've started up a solution and for some reason its been set to release but I didn't spot it. What does the code look like? AB "PeteOlcott" <PeteOlcott@gmail.com> wrote in message news:f2155ab0-d6b7-438e-a6db-89772f63e283@75g2000hso.googlegroups.com... On Oct 15, 11:36 am, "Adam Benson" <Adam.Ben...@NOSPAMMYSPAM.omnibus.co.uk> wrote: > Are you absolutely sure the code that's being run (.exe and .dll's I mean, > not source code) matches your source code? > > "PeteOlcott" <PeteOlc...@gmail.com> wrote in message > > news:2a0dca19-8634-4301-92d7-cf648c1ef278@b31g2000prb.googlegroups.com... > > > > >I set a breakpoint in a .NET function, and the F10 [Step Over] debug > > option never reaches many of the source lines in this function. The > > lines that it skips are not part of a conditional expression thus > > should always get invoked.- Hide quoted text - > > - Show quoted text - Yes, it does exactly the same thing immediately after a Rebuild Solution. |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|