Scribd
Upload
39 views5 pages

Dobbins Debugging

This document discusses debugging in the Visual Basic Integrated Development Environment (VB IDE). It defines debugging, describes different types of errors, and outlines the steps and tools used in debugging including print statements, breakpoints, stepping, watches, and sources of additional information.

Uploaded by

aditya sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
39 views5 pages

Dobbins Debugging

This document discusses debugging in the Visual Basic Integrated Development Environment (VB IDE). It defines debugging, describes different types of errors, and outlines the steps and tools used in debugging including print statements, breakpoints, stepping, watches, and sources of additional information.

Uploaded by

aditya sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Debugging in the Visual Basic

Integrated Development
Environment (VB IDE)

Elizabeth (Liz) Dobbins


Jan. 21, 2009

What is Debugging?
• Debugging is a methodical process of
finding and reducing the number of
bugs, or defects, in a computer program
or a piece of electronic hardware thus
making it behave as expected.
(Wikipedia, 1/16/2009)
• Successful debugging depends on the
skill of the programmer.

1
Types of Errors
• Compile Time (syntax)
• VB error scanning detects errors made on a single
line.
• Run Time
• Failure during run time (eg. divide by zero)
• IDE gives an error message and highlights
offending line.
• Logical
• Program doesn’t behave as expected.

Steps in Debugging
1) Reproduce the bug, and identify
conditions which produce it.
2) Simplify the program to isolate the
bug.
3) Investigate program’s execution.
a) Use tracing (i.e. print statements)
b) Use debugger tools provided by IDE

2
Tracing - Print & Assert
Syntax: Debug.Print expression
Behavior: Prints values of variables or
expressions as text in the “Immediate”
window.

Syntax: Debug.Assert (expression)


Behavior: Forces a design-time break at the
Assert statement when the expression
evaluates to False. If the expression
evaluates as True, program operation
continues.

Debugger Tools
• Control the program’s execution:
• Step Into/Over/Out
• Breakpoints
• Drag yellow highlight bar in code
• Investigate the values of variables and
expressions:
• Watch Window
• Local Window
• Report over cursor
• All available through menu, toolbar, keyboard
shortcuts, right-click menu

3
Step Into/Over/Out
• Step Into starts program then stops
before 1st executable, or steps line by
line. Enters subroutines and functions.
• Step Over skips current line (but not its
execution). Doesn’t enter subroutines
or functions.
• Step Out leaves current subroutine and
pauses at next expression in the calling
code.

Breakpoints
• Internal stopping or pausing place in a
program
• Run to breakpoint, then examine
variable values. Easier than stepping.
• Multiple ways to “toggle” on/off

4
Watches
• Real-time report of a variable or value of
an expression
• Local window shows all variables in
subroutine.
• If that’s too many, add select variables
to Watch window.
• Quick Watch adds variables quickly to
Watch window.

Sources of Information
• VB IDE help [F1] (Print and Assert)
• Web based tutorials
• http://www.virtualsplat.com/tips/visual-basic-debugging.asp
• Microsoft Support
• Overview of Visual Basic Editor Debugging Tools
(http://support.microsoft.com/kb/165517)
• Tips for Debugging Visual Basic for Applications Code
(http://support.microsoft.com/kb/142999) - old Access
• ESRI Support
• http://edndoc.esri.com/arcobjects/8.3/gettingstarted/vbspecifi
cs.htm#Debugging_Visual_Basic_Code

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy