Home > Archive > Visual Basic > July 2006 > VB debug problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Ben Whyte 2006-07-04, 7:55 am |
| Hi
I have an odd problem with VB debugging that I haven't come across
before and wondered if anyone else had.
When I step over lines of code in my project, it still steps into
certain subs or functions that are called in the line I am stepping over.
This happens to some developers on our project not all.
There are no break points in those modules.
Any ideas ?
Ben
| |
| Tony Proctor 2006-07-04, 7:55 am |
| Do you have any watchpoints enabled? Ben Do you call on the 'Stop' command,
or 'Debug.Assert'? Are those procedures raising any errors (you may have
'break on All Errors' enabled)?
If you just hit F5, goes the program break at a particular instruction in
one of those procedures, or just go flying through? If the former then the
statement it broke at will be of interest. If the latter then it sounds like
a potential stack corruption that's changing the IDE equivalent of the
processor status word's T-bit.
Tony Proctor
"Ben Whyte" <news@whyte-systems.co.uk> wrote in message
news:elKrE$1nGHA.4172@TK2MSFTNGP03.phx.gbl...
> Hi
>
> I have an odd problem with VB debugging that I haven't come across
> before and wondered if anyone else had.
>
> When I step over lines of code in my project, it still steps into
> certain subs or functions that are called in the line I am stepping over.
>
> This happens to some developers on our project not all.
>
> There are no break points in those modules.
>
> Any ideas ?
>
> Ben
| |
| Ben Whyte 2006-07-04, 7:55 am |
| Hi Tony
No watch points, or calls to anything else.
f5 and it just shoots straight by without stopping. Also it does the
same with run to cursor.
Ben
Tony Proctor wrote:
> Do you have any watchpoints enabled? Ben Do you call on the 'Stop' command,
> or 'Debug.Assert'? Are those procedures raising any errors (you may have
> 'break on All Errors' enabled)?
>
> If you just hit F5, goes the program break at a particular instruction in
> one of those procedures, or just go flying through? If the former then the
> statement it broke at will be of interest. If the latter then it sounds like
> a potential stack corruption that's changing the IDE equivalent of the
> processor status word's T-bit.
>
> Tony Proctor
| |
|
|
"Ben Whyte" <news@whyte-systems.co.uk> wrote in message
news:uy5wPe2nGHA.4728@TK2MSFTNGP05.phx.gbl...
> Hi Tony
>
> No watch points, or calls to anything else.
>
> f5 and it just shoots straight by without stopping. Also it does the
> same with run to cursor.
>
> Ben
>
<snipped>
I have seen the phenomena while stepping thru code; VB will skip over
several lines of code. Never been able to determine the exact cause, but it
appears related to conditions where the project contains modules in
different folders or is employing utilities to manage files outside the IDE
while the IDE is running.
The "cure" is to shutdown VB and cleanout the project folders (VSS is very
helpful here). Make sure all project files are read/write. Reopen VB and do
a make - repair any syntax or reference errors. The problem will then
resolve itself.
hth
-ralph
|
|
|
|
|