Debugger crashing after F5

[Constantin--P]

Hello Electrolund,

From your log I can see that after hitting continue there is no communication between CVI and the debugger. Initially I suspected that there is intense comunication due to big amount of watchpoints and other debugging stuff, but it's not the case.

The other 2 errors windows you got I can see if I kill cvidebug.exe while stopped at a breakpoint.

When you hit continue does the program continue or it is also stopped?

Could you make a copy of the project to a location that is not linked to SVN and see if it also happens in this case.

Constantin

[ElectroLund]

When I hit continue, or even Go To Cursor (F7), the cvidebug.exe will hange and the cvi.exe appears as if it is crashed.  If I kill cvidebug.exe, cvi.exe throws that dialog that states "...did not receive a reply to a debugging message ."  At this point CVI returns from the brink.  But I have to click the debug green arrow button again to re-enter debugger.

I will have to try the copy of the project in a non-SVN capacity.  Updates to follow...

[Constantin--P]

I was asking about the program written in CVI you are debugging. Does it continue or it stays frozen?

[ElectroLund]

No, it crashes too. When I click on any of its panels, there's no response.

[ElectroLund]

Ok, I have some results of the test.  Here's how I set it up:

• Rebooted my Win7 Pro machine.
• I copied all the source files and necessary DLLs specific to my project to a new project directory.  I didn't copy anything else. 
• I regenerated the PRJ and CWS files and their build folders with a make command.
• Debug windows: zero watch variables, all closed during debug.

Then I did a similar breakpoint test.  Same cvidebug.exe crash as other original SVN-based project.  Here's the breakpoint setup that produced the crash:

[ElectroLund]

Here's another interesting clue.  This project is now consuming about 100 MB of my PC RAM (!) when loaded.

By comparison, two other projects take about:

• 39.5 MB
• 36.9 MB

These two projects are considerably smaller in scale.  But who cares?!  These RAM measurements are just cvi.exe when the CWS file is first opened.  Not the debugger running.

So what in the world is chewing up that much more memory on the problem project?

[Constantin--P]

Hello Electrolund,

The high memory consumption is probably due to browse info since you have a fairly large project.

Could you disable browse info and see if the problem occurs in this case.

Constantin.

[ElectroLund]

Disabled browse info.  Re-did the test as shown above with the same breakpoint and F7 test.  cvidebug.exe hung there again.

On another note, since disabling the browse info completely, my memory consumption on this project is WAY down (~20MB from +100).

As a simple test, I played with the options for Browse Info and here are the memory footprints (MB):

• Disabled = 20-25
• On Save = 118
• On Edit = 118
• On Compile = 118

Despite the various ON types, they all consume a tremendous amount on large projects.

This is a real shame, since the feature is particluarly needed on larger projects.

[Constantin--P]

So the problem is not high memory consumption...

You said you had the same problem with another, completely different project. Was the other project also big?

It would be useful if you could reproduce this with a small project that you could post, otherwise I don't see any way to investigate further.

Constantin

[ElectroLund]

The other project is maybe half the size.  Also less than half the memory footprint too.

I will work on stripping this project down so that I can share it with you.  Is there a private mechanism for posting projects?