Scribd
Upload
462 views9 pages

ITK Debugging: Rajakumar Kasi

This document discusses debugging ITK code using Microsoft Visual Studio. It describes local and remote debugging, how breakpoints work to pause execution, debug configurations for ITK code in Visual Studio, and common shortcut keys used in the debugger.

Uploaded by

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

ITK Debugging: Rajakumar Kasi

This document discusses debugging ITK code using Microsoft Visual Studio. It describes local and remote debugging, how breakpoints work to pause execution, debug configurations for ITK code in Visual Studio, and common shortcut keys used in the debugger.

Uploaded by

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

ITK debugging

Rajakumar Kasi

Introduction
A debugger allows you, the
programmer, to interact and inspect
the running program, making it
possible to trace the flow of
execution and track down the
problems.
TC 9.1 ITK MS Visual studio 2008
SP1.

Types
Local Debugging
Local debugging involves running the program you are debugging runs
on the same machine as the debugger
Debugging locally has the least amount of latency involved

Remote Debugging

Remote debugging means that the program your debugging is running on a separate machine
and the debugging takes place on an isolated box.
Remote debugging usually takes place over a network connection, so there is some latency
issues to deal with.
Visual studio has a special program that is used to set up a remote debugging session.
Other than the fact that the process is running on a separate machine, debugging remotely is
really no different than running locally from the perspective of the IDE.

Breakpoints
Breakpoints are simply spots in the code that are marked to tell the
debugger to stop the programs execution at that point when the
program counter is set for that particular line in code.
Breakpoints can also be set up to execute on a specified condition.
breakpoints are the cornerstone of effective debugging.

Debug configuration for


ITK code
In the configuration dialog
box
Configuration properties -> C/C++ ->
General ->Additional include directories
points to
C:\Users\Public\Documents\teamcenter\i
nclude
Configuration properties -> C/C++ ->
Preprocessor -> Preprocessor definitions
to IPLIB=none

Debug configuration for ITK


code Contd
Configuration properties -> Linker ->
General -> Additional Library Directories to
C:\Progra~1\Siemens\Teamcenter9\c3png\li
b

Configuration properties -> Linker -> Input


-> Additional dependencies to itk_main.obj
C:\Progra~1\Siemens\Teamcenter9\c3png\li
b\*.lib

Debug
Debug flag
PDB file.

Shortcut keys
F5
- Start debugging or stop at next
breakpoint or application exit or exception
thrown or you choose Stop Debugging on the
Debug menu
Ctrl + F5 - Start without debugging.
Shift + F5 Stop debugging
Ctrl + Shift + F5 Restart debugging
F10 - Step over the line of code
F11 - Step into a function
Shift+F11 Step out of a function

Shortcut keys

Contd

Ctrl + Alt + Q Launch quick watch


dialog box
F9 - Toggle breakpoint
Ctrl + Shift + F9 Delete breakpoint
Ctrl + Alt + E Launch Exception
dialog box

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