valgrind에 대해서 궁금한 것이 있습니다.

3.5.2 Valid-address (A) bits
Notice that the previous subsection describes how the validity of values is established and maintained without having to say whether the program does or does not have the right to access any particular memory location. We now consider the latter issue.
As described above, every bit in memory or in the CPU has an associated valid-value (V) bit. In addition, all bytes in memory, but not in the CPU, have an associated valid-address (A) bit. This indicates whether or not the program can legitimately read or write that location. It does not give any indication of the validity or the data at that location -- that's the job of the V bits -- only whether or not the location may be accessed.

Every time your program reads or writes memory, Memcheck checks the A bits associated with the address. If any of them indicate an invalid address, an error is emitted. Note that the reads and writes themselves do not change the A bits, only consult them.

So how do the A bits get set/cleared? Like this:

When the program starts, all the global data areas are marked as accessible.

When the program does malloc/new, the A bits for the exactly the area allocated, and not a byte more, are marked as accessible. Upon freeing the area the A bits are changed to indicate inaccessibility.

When the stack pointer register (%esp) moves up or down, A bits are set. The rule is that the area from %esp up to the base of the stack is marked as accessible, and below %esp is inaccessible. (If that sounds illogical, bear in mind that the stack grows down, not up, on almost all Unix systems, including GNU/Linux.) Tracking %esp like this has the useful side-effect that the section of stack used by a function for local variables etc is automatically marked accessible on function entry and inaccessible on exit.

When doing system calls, A bits are changed appropriately. For example, mmap() magically makes files appear in the process's address space, so the A bits must be updated if mmap() succeeds.

Optionally, your program can tell Valgrind about such changes explicitly, using the client request mechanism described above.