No longer stopping for breakpoints

Hi Gang-

I've got two machines, a 32 bit desktop and a 64 bit laptop. Visual Studio 2010 on both. Developing a Grasshopper plugin, all has been working fine for months.

However, sometime in Dec the 64 bit laptop stopped stopping for breakpoints in VS2010. The other machine still works fine, I'm compiling the same code. The plugins run fine on both machines. The GrasshopperDeveloper settings are the same... I reinstalled Rhino 5 and Grasshopper... But the laptop now ignores breakpoints.

I don't know what else to look at for things that might make one build environment catch breakpoints and the other not. Are there any clues for other possible causes?

Thanks!

- Brian -

▶ Reply to This

Replies to This Discussion

Permalink Reply by Giulio Piacentino on January 5, 2012 at 2:05am

Hi Brian,

several things might cause it:

the built .gha is not the one that is actually loaded. It is residing in another location.
the build process does not produce a .pdb file with the same date and time as the .gha file
the .gha file is in release mode
_GrasshopperDevelopeSettings "Memory Load" is checked (this impedes debugging)
the runtime used by Rhino is younger than the debugger used by VS (improbable if using Rhino 5 and VS2010)
...several other causes

What happens when you click the "pause" button in VS, after having started Rhino with the VS "play" button?

- Giulio
_________________
giulio@mcneel.com

▶ Reply

Permalink Reply by Brian Lockyear on January 5, 2012 at 3:25pm

Thanks so much for the help & ideas... still not making it happen yet.

Looked for stale .gha files, can add and remove a new component from my build and see it in the menu so that seems okay.

.pdb file has same date and time.

not sure re release mode but it looks like debugging symbols are included and optimize code is turned off

developer settings has mem load unchecked

not sure how to verify runtimes...

when I click pause I get an error message saying "Unable to break execution. This process is not currently executing the type of code that you selected to debug."