Browse Prior Art Database

Graphical Representation of Memory In a Debugger

IP.com Disclosure Number: IPCOM000115347D
Original Publication Date: 1995-Apr-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 27K

Publishing Venue

IBM

Related People

Kolar, RN: AUTHOR

Abstract

Disclosed is a time saving and efficient way of graphically representing the memory in a debugger. During the debugging of an application, the memory used by an application cannot usually be seen graphically (unless the debugger provides this capability). As a result, problems due to illegal memory overwrite which usually show up as future problems, are hard to debug and could be highly time consuming.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Graphical Representation of Memory In a Debugger

      Disclosed is a time saving and efficient way of graphically
representing the memory in a debugger.  During the debugging of an
application, the memory used by an application cannot usually be seen
graphically (unless the debugger provides this capability).  As a
result, problems due to illegal memory overwrite which usually show
up as future problems, are hard to debug and could be highly time
consuming.

      The solution is to provide a graphical representation of the
application memory in the debugger.  The programmer should be able to
set breakpoints before a memory write operation and graphically be
able to see if a memory overwrite occurred over an illegal address
space for that operation.  The valid address spaces for an operation
are shaded using a color i.e., green.  Immediately after the
operation, the space that is illegally written into is shown using a
different color i.e., red.  This way, memory overwrite problems can
be detected very early, thus, saving debugging time and enabling the
programmer to be more efficient.