Describe the functions of the debugger screen.

- Single step(F5) - Use this option to step through the program statement by
statement. This allows you to branch into subroutines and function modules, and to
execute these routines step by step as well. Once a subroutine or function module
has been processed, control returns to the statement following the CALL FUNCTION
or PERFORM statement.

- Execute(F6)- Use this option to process a program line by line. All of the
statements on the current line are processed in a single step. If you are positioned
on a line that calls a subroutine and you choose Execute, the Debugger processes
the whole subroutine and then moves on to the line following the subroutine call. This
allows you to jump through the statements within the subroutine.

- Return(F7) - The Debugger returns from a routine to the point at which control
returns to the main program. Use this option to return from a subroutine, function
module, or called program to the calling program.

- Continue(F8)- Use this option to process the program up to the next dynamic or
static breakpoint or up to the cursor position. If there are no more breakpoints in the
program and no cursor has been set, the system exits debugging mode and
executes the rest of the program normally.

- Tables - Display the contents of internal tables.
Click Here to Read More !!!!

New Debugger

This section of the ABAP Workbench documentation provides information on how to use the New Debugger as a test tool for finding errors in the source code of an ABAP program.

Topics:

Overview of Functions


Concept and Limitations

Starting and Exiting

Control

Watchpoints

Breakpoints

Analyzing Source Code

Tools

Data Explorer

Screen Analysis

Breakpoints/Watchpoints and Checkpoints

Editor

Stack

Overview of Variables

Structure Display

Table Display

Object Display

Detailed Display

Editor (Edit Control)

Diff Tool

Loaded Programs (Global Data)

System Areas

User Interface

Layout of the User Interface

Designing Work Areas

Other Functions

System Debugging

Debugging in Production Clients

Error Handling


Other Related Links :
Debugger
Classic Debugger
Click Here to Read More !!!!

Classic Debugger

This section of the ABAP Workbench documentation provides information on how to use the

Debugger as a test tool for finding errors in the source code of an ABAP program.

Topics:

Overview of Functions

Starting the Classic Debugger

Display-Modes in the Classic Debugger

Release Changes
Breakpoints

Static Breakpoints

Dynamic Breakpoints

Breakpoints at Statements

Breakpoints at Subroutines

Breakpoints at Function Module Calls

Breakpoints at Methods

Breakpoints at System Exceptions

Saving Breakpoints

Managing Dynamic Breakpoints

Watchpoints

Setting Watchpoints

Specifying Logical Links

Changing Watchpoints

Memory Monitoring with Watchpoints

Analyzing Source Code

Displaying the Source Code

Stepping Through the Source Code

Processing Fields

Processing Internal Tables

Attributes of Data Objects

Displaying OO Objects

Other Functions

Displaying Lists

Call Links

Debugging in Production Clients

Releasing Database Locks

Settings and Warnings

Memory Use

Memory Analysis

Sessions


Other Related Links :

• Debugger
• New Debugger
  
  
  
  

Click Here to Read More !!!!

Debugger

The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.
Two types of debugging are currently possible: Debugging with the classic Debugger for release levels up to and including 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:

· The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.

The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means.
The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.

As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the Debugger at any time during a session under the menu option Debugging.
As of Release 7.00, the new ABAP Debugger is the default.


Other Related Links :

• Classic Debugger
• New Debugger

Click Here to Read More !!!!