JP2014052753A - Memory management device, and memory management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To properly process a pointer area in the case of releasing a dynamic memory.SOLUTION: A memory management device of this invention includes translation means for adding notification processing for notifying an operation of a pointer area associated with a heap memory in processing of an application program to the application program, and memory management means for receiving notification from the notification processing, recording the operation of the pointer area due to release of the heap memory on the basis of the notification, and invalidating the pointer area corresponding to the released heap memory.

Description

  The present invention relates to a memory management device, and more particularly to management of a storage area that is dynamically secured.

  An information processing device including a central processing unit (CPU) dynamically secures a storage area such as a memory when executing a program. Such a storage area that is dynamically secured is called a heap memory or a heap area.

  The heap memory is an important function that is indispensable for advanced programs and object-oriented programs, unlike the static memory, which increases the degree of freedom of memory usage.

  In a general information processing apparatus, an operating system (OS) that operates on the information processing apparatus provides heap memory to a program. However, the OS does not manage the heap memory after provision. A program developed by a program developer needs to manage heap memory used in the program.

  The management of the heap memory implemented by the program requires the heap memory that is no longer needed to be released in addition to the management of the heap memory in use (generally using a pointer).

  The heap memory is often realized as a reserved memory pool. The heap memory once secured is managed as an unused area by the OS side after being released by the program. When the heap memory is requested from the program, the OS provides an unused area after the release as a new heap memory.

  As described above, the heap memory may be used for different purposes according to the processing flow of the program even at the same address.

  For this reason, if the address of the released heap memory is erroneously referred to, the program will cause an operation error or memory data corruption.

  In addition, the heap memory capacity has an upper limit. If the program does not properly release heap memory that is no longer used, the OS will run out of heap memory to provide. Therefore, a program that operates for a long time needs to release the heap memory appropriately in order not to cause a shortage of heap memory.

  As a function of processing the released heap memory, there is a garbage collection (GC). In recent years, heap memory equipped with GC has been used. However, heap memories with GC are expensive and limited to specific applications. Moreover, since it is difficult to implement a CG function in a program, it is not generally performed.

  For this reason, the program developer performs confirmation work on heap memory management at each stage of program development.

  For example, the developer eliminates heap memory management errors by repeating desktop debugging, program testing, and debugging work at the time of program specification review and source coding stage.

  Thus, heap memory management is a heavy burden for program developers. In particular, when an illegal operation or memory corruption occurs due to an illegal pointer access, the identification of the cause and correct correction of the program are a heavy burden on the developer.

  In recent years, several devices for detecting an illegal operation of a program have been proposed. However, such a device is expensive. Moreover, in order to use such a device, specialized knowledge is required. For this reason, general development sites cannot be easily introduced yet.

  Therefore, a program for verifying the operation of the heap memory has been proposed (see, for example, Patent Document 1).

JP 2008-276763 A

  The detection method described in Patent Document 1 detects fraud of a pointer related to a heap memory. In order to detect fraud, the detection method described in Patent Document 1 incorporates an API function for confirming the contents of the pointer in the program source code.

  In other words, the detection method described in Patent Document 1 is an invention for detecting fraud using a pointer reference.

  However, as described above, the heap memory is released based on the operation of the program. When the heap memory is released, the program generates an error when using the point for the heap memory released by the program. Therefore, when the heap memory is released, the program needs to process a pointer to the released heap memory.

  That is, the detection method described in Patent Document 1 has a problem in that it cannot process the pointer when the heap memory is released.

  An object of the present invention is to solve the above problems and provide a memory management device and a memory management method capable of appropriately processing pointers when heap memory is released.

  The memory management device according to the present invention receives a notification from the notification process, a translation unit that adds a notification process for notifying an operation of a pointer area related to a heap memory in the process of the application program, and receives the notification from the notification process. And a memory management unit that records the operation of the pointer area associated with the release of the heap memory and invalidates the pointer area corresponding to the released heap memory.

  The memory management method of the present invention adds a notification process for notifying an operation of a pointer area related to a heap memory in the process of an application program to the application program, receives a notification from the notification process, and based on the notification, The operation of the pointer area associated with the release of the heap memory is recorded, and the pointer area corresponding to the released heap memory is invalidated.

  The program of the present invention receives a notification from the notification process, a process for adding a notification process for notifying an operation of a pointer area related to the heap memory in the process of the application program, and a notification from the notification process. A computer is caused to execute a process for recording a pointer area operation associated with the release of the heap memory and a process for invalidating the pointer area corresponding to the released heap memory.

  According to the present invention, the pointer can be appropriately processed when the heap memory is released.

FIG. 1 is a block diagram showing an example of an information processing system including a memory management device according to the first embodiment of the present invention. FIG. 2 is a block diagram illustrating an example of the configuration of the memory management device according to the first embodiment. FIG. 3 is a diagram illustrating an example of pointer area information according to the first embodiment. FIG. 4 is a diagram illustrating an example of information related to the change of the pointer area according to the first embodiment. FIG. 5 is a block diagram illustrating an example of a configuration of a memory management device according to a modification of the first embodiment. FIG. 6 is a block diagram illustrating an example of a configuration of a memory management device according to a modification of the first embodiment. FIG. 7 is a block diagram illustrating an example of a configuration of a memory management device according to a modification of the first embodiment.

  Next, embodiments of the present invention will be described with reference to the drawings.

  Each drawing explains an embodiment of the present invention. Therefore, the present invention is not limited to the description of each drawing. Moreover, the same number is attached | subjected to the same structure of each drawing, and the repeated description may be abbreviate | omitted.

(First embodiment)
FIG. 1 is a block diagram showing an example of the configuration of an information processing system 60 including a memory management device 20 according to the first embodiment of the present invention.

  The information processing system 60 includes a CPU 10, a memory management device 20, a memory unit 30, a ROM (Read Only Memory) 40, and an internal storage device 50.

  The ROM 40 includes fixed data used in the information processing system 60 and an initialization program (IPL: Initial Program Loader).

  The memory unit 30 is a memory used by the CPU 10.

  The internal storage device 50 stores data and programs stored in the information processing system 60 for a long time.

  The CPU 10 performs processing of the information processing system 60.

  For example, the CPU 10 reads the OS 310 from the internal storage device 50 based on the IPL of the ROM 40, stores it in the memory unit 30, and starts (starts up) the operation based on the OS 310.

  After starting the operation in the OS 310, the CPU 10 reads the application program 320 from the internal storage device 50 to the memory unit 30 and executes it based on a user instruction or the like.

  When executing the application program 320, the CPU 10 secures and uses the static memory 330, the stack memory 340, and the heap memory 350 on the memory unit 30 as necessary.

  The memory management device 20 according to the present embodiment manages the memory unit 30 including the heap memory 350 and manages operations related to the dynamically reserved memory. In particular, the memory management device 20 manages pointers associated with releasing the heap memory 350.

  Note that the number of pointers is not limited to one, and a plurality of pointers are generally declared. When multiple declarations are made, the pointer occupies a predetermined range (pointer area) of the storage area. Therefore, the following description will be given as a “pointer area” including one case.

  The memory management device 20 will be further described with reference to the drawings.

  FIG. 2 is a block diagram illustrating an example of the configuration of the memory management device 20 according to the present embodiment.

  The memory management device 20 includes a translation unit 210, a memory management unit 220, and an unauthorized access specifying unit 230.

  First, the translation unit 210 will be described.

  The translation unit 210 incorporates a mechanism for notifying the memory management unit 220 of the application program 320 when a compiler (not shown) creates (compiles) the application program 320 based on the source text (source code or source file). More specifically, the translation unit 210 adds notification processing for the operation of the pointer area to the application program 320.

  Therefore, the translation unit 210 includes a pointer area registration unit 211, a pointer area change recording unit 212, a heap address notification unit 213, and a stack area notification unit 214.

  The pointer area registration unit 211 registers (notifies) information on the pointer area to be used in the memory management unit 220 in the part of the application program 320 where the pointer area is declared (hereinafter referred to as “pointer area registration process”). Add Note that the declaration of the pointer area may be referred to as securing the pointer area.

  The pointer area used in the application program 320 generally has the following types.

  (1) Pointer area declared in the static memory 330: It is often declared at the start of the application program 320.

  (2) Pointer area declared in the stack memory 340: Generally, when calling a function, it is often declared as a local variable or an argument.

  (3) Pointer area declared in the heap memory 350: Declared when the heap memory 350 is secured.

  The pointer area registration unit 211 adds a pointer area registration process to the process of registering the pointer area of the application program 320. However, the pointer area registration unit 211 does not need to add pointer area registration processing to all of the above three types. For example, static memory 330 is not freed during operation of application program 320. Therefore, the pointer area registration unit 211 may not add pointer area registration processing to the pointer area used in the static memory 330.

  FIG. 3 is a diagram showing an example of pointer area information notified to the memory management unit 220 in a table format.

  The pointer area information shown as an example in FIG. 3 includes a pointer name, a source text name, a line number, address information, and a status.

  The pointer name is the name of the declared pointer area.

  The source text name is the name of the source text compiled by the compiler.

  The line number is the line number where the pointer area is declared in the source text.

  The address information is address information of the memory referred to by the pointer area.

  The state is information indicating the state of the declared pointer area. For example, when a pointer is declared, the state is “generated”.

  Returning to the description using FIG.

  The pointer area change recording unit 212 notifies the memory management unit 220 of information related to the change of the pointer area in the process of changing the contents of the pointer area of the application program 320 (hereinafter referred to as “pointer area change notification process”). Add

  The pointer area change recording unit 212 operates corresponding to the pointer area registered by the pointer area registration unit 211. Therefore, for example, when the pointer area registration unit 211 does not add processing to the static memory 330, the pointer area change recording unit 212 does not add processing to changes in the static memory 330.

  FIG. 4 is a table showing an example of information related to the pointer area change notified to the memory management unit 220 in a table format.

  The information regarding the change of the pointer area shown as an example in FIG. 4 includes, for example, a source text name, a line number, a thread identifier (ID: Identifier), and a state.

  The source text name and line number are the same as in FIG.

  The thread ID is an ID of a thread that has changed (operated) the pointer area in the application program 320.

  The state is the same as the state of FIG. For example, when a value is set in the pointer area, the state is “set”.

  Returning to the description using FIG.

  The heap address notification unit 213 adds a process of notifying the memory management unit 220 of the release of the heap memory 350 (hereinafter referred to as “heap memory release notification process”) to the process of releasing the heap memory 350 of the application program 320. . Further, the heap address notifying unit 213 notifies the memory management unit 220 of information related to the change in the size of the heap memory 350 in the process of changing the size of the heap memory 350 in the application program 320 (hereinafter referred to as “the heap memory 350”) , "Heap memory range change notification process") is added.

  Hereinafter, “heap memory release notification processing” and “heap memory range change notification processing” are collectively referred to as “heap memory change notification processing”.

  Note that releasing the heap memory 350 is the same as changing the range of the heap memory 350 to “0”. Therefore, the heap address notification unit 213 may perform “heap memory change notification processing” without distinguishing between “heap memory release notification processing” and “heap memory range change notification processing”.

  The stack area notification unit 214 adds a process of notifying the memory management unit 220 of information related to the operation of the stack memory 340 (hereinafter referred to as “stack operation notification process”) to the process of operating the stack memory 340 of the application program 320. To do.

  As described above, the translation unit 210 according to the present embodiment adds a process in which the pointer area registration unit 211 notifies the pointer area information when the stack memory 340 is secured and when the heap memory 350 is secured. To do.

  For this reason, the heap address notification unit 213 may add a process for notifying the memory management unit 220 when the heap memory 350 is released or changed.

  Similarly, the stack area notification unit 214 may add a “stack operation notification process” to the process of releasing the stack memory 340 (for example, when returning from the called function to the reading source).

  However, the configuration of the translation unit 210 is not limited to this. The translation unit 210 may have a configuration for each memory. For example, the translation unit 210 may include a processing unit that processes the heap memory 350. Then, the processing unit that processes the heap memory 350 adds a pointer area registration notification process to the process of declaring a pointer area in the heap memory 350, and adds a heap memory release notification process to the heap memory 350 release process. You may do it.

  Next, the memory management unit 220 will be described.

  The memory management unit 220 manages the pointer area based on the notification from the mechanism (notification processing) incorporated in the application program 320 by the translation unit 210.

  Therefore, the memory management unit 220 includes a pointer area management unit 221, a pointer area initialization unit 222, and a pointer area operation recording unit 223.

  The pointer area management unit 221 manages pointer area information based on notifications from the processes incorporated in the translation unit 210.

  The pointer area initialization unit 222 initializes the pointer area based on an instruction from the pointer area management unit 221.

  The pointer area operation recording unit 223 stores the pointer area operation (change of state) based on an instruction from the pointer area management unit 221.

  As described above, in the memory management unit 220 according to the present embodiment, the pointer area management unit 221 performs processing related to the pointer area with the center.

  Therefore, the memory management unit 220 will be described in more detail with a focus on the operation of the pointer area management unit 221.

  The pointer area management unit 221 receives a notification from each process incorporated in the translation unit 210 and manages the pointer area. These processes will be described corresponding to each process incorporated in the translation unit 210.

  First, an operation corresponding to the “pointer area registration process” will be described.

  When the notification from the “pointer area registration process” is received, the pointer area management unit 221 records (registers) the received pointer area information in the pointer area operation recording unit 223. Further, the pointer area management unit 221 issues an instruction to the pointer area initialization unit 222 to initialize the registered pointer area. The pointer area management unit 221 may record in the pointer area operation recording unit 223 that initialization has been completed after initialization.

  Next, an operation corresponding to the “pointer area change notification process” will be described.

  Upon receiving a notification regarding the change of the pointer area from the “pointer area change notification process”, the pointer area management unit 221 records the change (operation) in the pointer area operation recording unit 223 based on this notification.

  Next, an operation corresponding to the “heap memory change notification process” will be described.

  The “heap memory change notification process” is a “heap memory release notification process” and a “heap memory range change notification process”.

  In the case of notification from the “heap memory release notification process”, the pointer area management unit 221 records the pointer area included in the released heap memory 350 as a non-management target (invalid) in the pointer area operation recording unit 223. To do. Furthermore, the pointer area management unit 221 uses the pointer area initialization unit 222 to initialize the pointer area as a non-target.

  Based on this processing, the memory management device 20 invalidates the pointer area corresponding to the released heap memory 350. As a result, the application program 320 can appropriately process the pointer area corresponding to the released heap memory 350.

  In the case of notification from the “heap memory range change notification process”, the pointer area management unit 221 calculates the range of the released heap memory 350 and the range of the added heap memory 350.

  Then, the pointer area management unit 221 sets the pointer area corresponding to the released range of the heap memory 350 to be excluded (invalid) as in the case of the notification from the “heap memory release notification process”, and further, the pointer area Initialize the area.

  If there is a pointer area corresponding to the range of the added heap memory 350, the pointer area management unit 221 records the pointer area information in the pointer area operation recording unit 223, and uses the pointer area initialization unit 222. Initialize the pointer area.

  Based on this processing, the memory management device 20 invalidates the pointer area corresponding to the released heap memory 350. As a result, the application program 320 can appropriately process the pointer area corresponding to the released heap memory 350.

  Next, an operation corresponding to the “stack operation notification process” will be described.

  In the case of notification from the “stack operation notification process”, the pointer area management unit 221 records the pointer area corresponding to the released stack memory 340 as a non-target (invalid) in the pointer area operation recording unit 223. Furthermore, the pointer area management unit 221 uses the pointer area initialization unit 222 to initialize the pointer area as a non-target.

  Based on this processing, the memory management device 20 invalidates the pointer area corresponding to the released stack memory 340. As a result, the application program 320 can appropriately process the pointer area corresponding to the released heap memory 350.

  Next, the unauthorized access specifying unit 230 will be described.

  When unauthorized processing such as unauthorized access occurs in the pointer area, the unauthorized access identifying unit 230 refers to the memory management unit 220 and identifies the location where the illegal processing in the pointer area has occurred. More specifically, when an illegal pointer area occurs, the unauthorized access identification unit 230 extracts information on the invalid pointer area from the pointer area operation recording unit 223 and identifies an unauthorized process.

  For example, the following process is assumed as an illegal process when the heap memory 350 is accessed by referring to the pointer area.

(1) Unauthorized access due to uninitialized contents (2) Unauthorized access based on unauthorized pointer value setting When unauthorized access occurs, the unauthorized access specifying unit 230, the pointer area operation recording unit 223 Check the record. For example, the unauthorized access specifying unit 230 refers to the information of the pointer area shown in FIG. 3 and specifies the source text and the number of lines in which the pointer area is declared. Further, the unauthorized access specifying unit 230 specifies the state of the pointer area, the position of the thread and the source text changed to the state based on the information related to the change of the pointer area shown in FIG.

  The developer can analyze fraud by referring to the information identified by the unauthorized access identifying unit 230.

  Therefore, the unauthorized access specifying unit 230 may include a function for notifying a developer or the like.

  As described above, the memory management device 20 according to the present embodiment can appropriately process the pointer area when the heap memory 350 is released.

  The reason is as follows.

  The translation unit 210 of this embodiment adds a process of notifying the memory management unit 220 to the process of securing (declaring), changing, and releasing the heap memory 350 of the application program 320.

  This is because the memory management unit 220 can exclude (invalidate) the pointer area corresponding to the released heap memory 350 based on the notification.

  Furthermore, the memory management device 20 can also appropriately manage the pointer area corresponding to the stack memory 340.

  The reason is as follows.

  The translation unit 210 according to the present embodiment adds a process of notifying the memory management unit 220 to the process of securing, changing, and releasing the stack memory 340 of the application program 320.

  This is because the memory management unit 220 can exclude (invalidate) the pointer area corresponding to the released stack memory 340 based on the notification.

  In addition, the memory management device 20 according to the present embodiment can obtain an effect of easily identifying unauthorized access.

  The reason is as follows.

  The memory management unit 220 of the present embodiment records the pointer area operation based on the notification added by the translation unit 210. This is because the unauthorized access identification unit 230 can identify unauthorized access in the pointer area based on the record.

<Modification>
Note that the configuration of the memory management device 20 of the present embodiment is not limited to the configuration described so far.

  For example, since the stack memory 340 is dynamically secured in the same manner as the heap memory 350, the stack memory 340 has been described.

  However, the memory management device 20 of the present embodiment may manage the heap memory 350 and the stack memory 340 as separate devices.

  The unauthorized access specifying unit 230 may be a separate device from the memory management device 20.

  FIG. 5 is a block diagram of an example of the configuration of the memory management device 25 that is an example of a modification.

  The memory management device 25 includes the same configuration as that of the memory management device 20 except that the unauthorized access specifying unit 230 and the stack area notification unit 214 are not included.

  Similarly to the memory management device 20, the memory management device 25 configured as described above can appropriately process the pointer area when the heap memory 350 is released.

  The reason is as follows.

  The translation unit 215 of this embodiment adds a process of notifying the memory management unit 220 to the process of securing, changing, and releasing the heap memory 350 of the application program 320.

  Then, based on the notification, the memory management unit 220 excludes the pointer area corresponding to the released heap memory 350 and records the operation.

  Furthermore, although the memory management device 25 of this embodiment includes the translation unit 215 and the memory management unit 220 in one device, the present invention is not limited to this. For example, as shown in FIG. 6, the memory management device 25 is configured such that the translation unit 215 and the memory management unit 220 are configured as another board connected via a bus or another device connected via a network. Also good. Note that the configuration shown in FIG. 6 is the minimum configuration of the present embodiment.

  In the description of the present embodiment, the memory management device 20 is described as a device different from the CPU 10, but the implementation of the memory management device 20 is not limited to this.

  For example, the function of the memory management device 20 may be realized by a program and incorporated in the OS 310 executed by the CPU 10. Alternatively, the memory management device 20 may be realized as an independent management program.

  The memory management device 20 may be stored in a recording medium that can be read by a computer (not shown) as a program that implements the functions of the memory management device 20. In that case, the CPU 10 may read and execute as a corresponding program of the memory management device 20 using a recording medium reading device (not shown).

  Alternatively, the memory management device 20 of the present embodiment includes a CPU different from the CPU 10, a ROM, a RAM (Random Access Memory), an IO (Input / Output) interface (hereinafter referred to as IO), and a NIC (Network Interface). Card).

  FIG. 7 is a diagram showing an example of the configuration of the memory management device 70 of this embodiment using the CPU 710.

  The memory management device 70 includes a CPU 710, a ROM 720, a RAM 730, an internal storage device 740, an IO 750, and a NIC 780, and constitutes a computer.

  The CPU 710 reads a program from the ROM 720 or the internal storage device 740. The CPU 710 implements the functions of the translation unit 210, the memory management unit 220, and the unauthorized access specifying unit 230 of the memory management device 20 based on the read program. The CPU 710 uses the RAM 730 and the internal storage device 740 as temporary storage when realizing each function. The CPU 710 is connected to other components such as the CPU 10 via the NIC 780.

  Note that the CPU 710 may read a program included in the storage medium 790 that stores the computer-readable program using a storage medium reading device (not shown). Alternatively, the CPU 710 may receive a program from an external device via a network (not shown).

  The ROM 720 stores programs executed by the CPU 710 and fixed data. The ROM 720 is, for example, a P-ROM (Programmable-ROM) or a flash ROM.

  The RAM 730 temporarily stores programs and data executed by the CPU 710. The RAM 730 is, for example, a D-RAM (Dynamic-RAM).

  The internal storage device 740 stores data and programs stored in the memory management device 70 for a long time. Further, the internal storage device 740 may operate as the pointer area operation recording unit 223. Further, the internal storage device 740 may operate as a temporary storage device for the CPU 710. The internal storage device 740 is, for example, a hard disk device, a magneto-optical disk device, an SSD (Solid State Drive), or a disk array device.

  The IO 750 connects the CPU 710 to the input device 760 and the display device 770. The IO 750 is, for example, an IO interface card.

  The input device 760 is an input unit that receives an input instruction from an operator of the memory management device 70. The input device 760 is, for example, a keyboard, a mouse, or a touch panel.

  The display device 770 is a display unit of the memory management device 70. The display device 770 is a liquid crystal display, for example.

  The NIC 780 mediates data exchange between the memory management device 70 and other components such as the CPU 10. The NIC 780 is, for example, a PCI (Peripheral Component Interface) card.

  The memory management device 70 configured as described above can obtain the same effects as the memory management device 20.

  This is because the CPU 710 of the memory management device 70 can realize the same operation as the memory management device 20 based on the program.

  While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

10 CPU
20 Memory management device 25 Memory management device 30 Memory unit 40 ROM
DESCRIPTION OF SYMBOLS 50 Internal storage device 60 Information processing system 70 Memory management apparatus 210 Translation part 211 Pointer area registration part 212 Pointer area change recording part 213 Heap address notification part 214 Stack area notification part 215 Translation part 220 Memory management part 221 Pointer area management part 222 Pointer Area initialization unit 223 Pointer area operation recording unit 230 Unauthorized access specifying unit 310 OS
320 Application program 330 Static memory 340 Stack memory 350 Heap memory 710 CPU
720 ROM
730 RAM
740 Internal storage device 750 IO
760 Input device 770 Display device 780 NIC
790 storage media

Claims (8)

Translation means for adding notification processing to the application program for notifying operation of a pointer area related to heap memory in processing of the application program;
A memory management unit that receives a notification from the notification process, records a pointer area operation associated with the release of the heap memory based on the notification, and invalidates the pointer area corresponding to the released heap memory. Management device. The memory management unit
Pointer area initialization means for initializing the pointer area;
Pointer operation recording means for recording information on the operation of the pointer area;
Based on the notification, the operation of the pointer area is recorded in the pointer operation recording means,
If the notification relates to the declaration of heap memory, the corresponding pointer area is initialized based on the pointer area initializing means,
When the notification relates to the release of the heap memory, the pointer operation recording unit records the invalidity of the pointer area corresponding to the released heap memory, and initializes the corresponding pointer area based on the pointer area initialization unit. The memory management device according to claim 1, further comprising pointer area management means. The translation unit
Pointer area registration means for adding the notification process to the process of declaring a pointer area;
Pointer area change recording means for adding the notification process to the process of changing the pointer area;
The memory management device according to claim 1, further comprising: a heap address notifying unit that adds the notification process to a process of releasing heap memory and a process of changing a range of the heap memory. The translation unit
The memory management device according to claim 3, further comprising: a stack area notifying unit that adds the notification process to a process of releasing the stack memory. The memory management device according to any one of claims 1 to 4, further comprising unauthorized access specifying means for specifying unauthorized access in the operation of the pointer area based on information recorded by the memory management means. A notification process for notifying the operation of the pointer area related to the heap memory in the process of the application program is added to the application program;
A memory management method for receiving a notification from the notification processing, recording an operation of a pointer area accompanying release of a heap memory based on the notification, and invalidating a pointer area corresponding to the released heap memory. Add the notification process to the process of adding a pointer area,
Add the notification process to the process of changing the pointer area,
The memory management device according to claim 6, wherein the notification processing is added to processing for releasing heap memory and processing for changing a heap memory range. A process of adding a notification process to the application program to notify the operation of the pointer area related to the heap memory in the process of the application program;
A process of receiving a notification from the notification process and recording a pointer area operation associated with the release of the heap memory and a process of invalidating the pointer area corresponding to the released heap memory based on the notification. The program to be executed.

Images