Fog Creek Software
Discussion Board

VB6 IDE question (probably bonehead)

Okay, so I've been seeing an occasional weird thing happen in my VB6 IDE (yes, I have SP5).  Sometimes, with no pattern I've yet been able to discern, it'll hang at a breakpoint.  When it does this, it'll refuse to do any variant of Step or Run, whether I try to invoke those commands from the keyboard, menu, or toolbar buttons.  The only thing I can do is end execution and try again.

If I click on the left margin where you'd normally be able to set a breakpoint, it overlays a green triangle on top of the breakpoint symbol.  (No, this is not the yellow triangle VB uses to indicate the execution point, but it's the same shape.)

There's probably a very simple explanation for this, but I've never seen this behavior before and could only find one reference to it on Deja (with no fix).  Any ideas?

Sam Livingston-Gray
Tuesday, January 06, 2004

I think your program crashed when you get the little green doohickey.

Tuesday, January 06, 2004

Reinstall VB. Some corrupt files probably.

Take this advise with a sea full of salt

Tuesday, January 06, 2004

You'd think so, but when there's no breakpoint, execution passes smoothly through that point.  I'm only screwed if I want to inspect something using the debugger.  (=

Sam Livingston-Gray
Tuesday, January 06, 2004

I have had some weirdness with the VB debugger.  Specifically not being able to debug some code but normal execution works. 

There isn't much I can suggest except to try and reset as much of your project as possible and try again. 

I've had VB programs that could actually corrupt the source code in IDE; the VB6 IDE has always been a little buggy in hard-to-trace ways.

Almost Anonymous
Tuesday, January 06, 2004

So may be inspecting something is what causes the problem? To get value of something debugger somtimes have to execute some code that very well could be unexpected at this point.

Have you ever added "i++" to watch window while stepping through loop in C++ :)

Tuesday, January 06, 2004

It's not the "break in class file" setting is it?

FWIW, I never have problems with VB. It works flawlessly.

Wednesday, January 07, 2004

If you do the following things a lot then VB can get VERY "squiffy" (it's better on NT family than 9x family)

a) Hit the stop button in the debugger. This means ActiveX components and your classes terminate events never get called properly. If you can it's nearly always better to exit out of your program nicely
b) Do a lot of coding while stopped in the debugger.
c) Use the "End" statement (it's a variant of (a))

Peter Ibbotson
Wednesday, January 07, 2004

Remember Sam, there are no boneheaded questions, just really boneheaded people. <g>

Pretty Fly For a White Guy
Thursday, January 08, 2004

The green triangle indicates that the line it is next to has *called* the currently executing line (where you see the yellow arrow). Any line in the call stack would show the green triangle.

I suspect your VB code calls some component, which does not return. What does the code next to the green triangle do?

Raj Chaudhuri
Monday, January 12, 2004

*  Recent Topics

*  Fog Creek Home