hi,
<b>NEW ABAP DEBUGGER AND MEMORY INSPECTOR</b>
<b>STARTING THE MEMORY INSPECTOR</b>
 LIFE ANALYSIS FROM INSIDE ABAP DEBUGGER, USING THE MI <b>PART OF THE DEBUGGER</b>  DEBUGGER MENU: GOTO -> STATUS DISPLAY -> MEMORY USE
 STAND-ALONE MEMORY INSPECTOR, ANALYZING MEMORY <b>SNAPSHOTS</b>
 TRANSACTION “S_MEMORY_INSPECTOR”
 FROM INSIDE THE DEBUGGER, COMPARING MEMORY <b>SNAPSHOTS</b>
 DEBUGGER MENU: DEVELOPMENT -> MEMORY ANALYSIS -> COMPARE MEMORY SNAPSHOTS
CREATING MEMORY SNAPSHOTS
 FROM INSIDE THE DEBUGGER
 DEBUGGER MENU: DEVELOPMENT -> MEMORY ANALYSIS -> CREATE MEMORY SNAPSHOT
 COMMAND /HMUSA IN THE COMMAND FIELD ON ANY SCREEN
 CALL THE WRITE_MEMORY_CONSUMPTION_FILE METHOD OF THE CL_ABAP_MEMORY_UTILITIES CLASS IN YOUR CODE. USE THIS OPTION CAREFULLY TO AVOID RUNNING OUT OF DISK SPACE
<b>BOUND MEMORY</b>
 MEMORY OF THE OBJECT “ITSELF”
 MINIMUM OF MEMORY THAT WILL BE FREED, IF OBJECT IS DELETED
<b>REFERENCED MEMORY</b>
 MEMORY OF THE OBJECT “ITSELF” AND ALL REFERENCED OBJECTS
 MAXIMUM OF MEMORY THAT CAN BE FREED, IF OBJECT IS DELETED
<b>FEATURES IN ABAP DEBUGGER</b>
 FILTER MEMORY OBJECTS
 SORT ACCORDING TO
 BOUND MEMORY
 REFERENCED MEMORY
 AGGREGATION OF TYPES (CLASS / DATA TYPE)
 FIND REFERENCES
 IDENTIFICATION AS PART OF A SSC
<b>CLASSIC DEBUGGER</b>
 DEBUGGER AND DEBUGGEE RUN IN THE SAME (INTERNAL) SESSION
 DEBUGGER DYNPROS PLACED “IN-BETWEEN”
<b>NEW ABAP DEBUGGER</b>
 MORE ROBUST DEBUGGER ARCHITECTURE
 POSSIBLE TO IMPLEMENT NEW FEATURES, FASTER AND WITH LESS RISKS.
 MORE FLEXIBLE.
 USE TWO SEPERATED SECTIONS FOR THE DEBUGGER AND THE APPLICATION.
<b>DEBUGGER TOOLS</b>
 UP TO 4 PARALLEL VISIBLE INSTANCES OF A TOOL (E.G. COMPARE 4 INTERNAL TABLES)
 TOOLS ARE INTEGRATED IN DEBUGGER FRAMEWORK AND BENEFIT FROM THE PROVIDED
SERVICES TO CUSTOMIZE THE UI. (CHANGE SIZE, POSITION, CLOSE TOOL ,…)
 TOOLS PROVIDE STANDARD SERVICES
STANDARD TOOLS – SOURCE DISPLAY, STACK, BREAKPOINTS, VARIABLES
<b>BREAKPOINTS</b>
 DEBUGGER CONTEXT OF CLASSIC ABAP DEBUGGER IS THE “INTERNAL SESSION”
 DEBUGGER CONTEXT OF NEW ABAP DEBUGGER IS THE “EXTERNAL SESSION”, I.E. THE “SAP-GUI WINDOW”
 CLASSIC DEBUGGER BREAKPOINTS ARE LOST, WHEN A NEW INTERNAL SESSION IS CREATED WHILE DEBUGGING (SUBMIT, CALL TRANSACTION,…)
 NEW DEBUGGER BREAKPOINTS ARE NEVER LOST
Message was edited by:
Armin Reichert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.