测量值的内存指针锁定装置电电气安全和61010。
Measurement value memory electrical pointer locking device electrical safety in accordance with IEC 61010.
每个新内存分配都需要到内存指针的更新，而随着这一动作发生得越来越多，会带来越来越多的资源消耗。
Each new memory allocation requires updates to the memory Pointers, and as this happens more and more, it creates more and more resource consumption.
不知道什么是对的对齐的你在这方面的认识，但情况类似，每个指针分配动态内存指针的数组。
Not sure what is your understanding of aligned in this context but the situation is similar to a array of Pointers where each pointer is allocated dynamic memory.
在什么地方namestr与其它地址数值一起被编写，从而丢失分配在main() 中的最后一个内存指针，最终导致渗漏吗？
Where exactly does namestr get written with another address value, and thereby lose the last pointer to memory allocated in main(), causing the leak?
它是指向这块内存的指针。
是的，一个指向这块内存的指针。
可能是泄漏、空指针或者错误的内存使用。
There might be leaks, dangling Pointers, or incorrect memory usage.
图中的箭头表示指向内存中下一个节点位置的指针。
The arrows in this diagram represent Pointers to the location of the next node in memory.
这个链表散列表包含有关共享内存日志标记指针的信息。
The linked list hash table contains information about the shared memory logging token pointers.
这会保存原来的堆栈指针，并自动分配堆栈内存。
This will save the old stack pointer and allocate stack memory atomically.
如果既没有根也没有指针指向链表，那么你的数据就丢失在内存中了。
If there is no root or a pointer pointing to any part of the list then your data is lost in memory.
就算您竭尽全力完成了上面的步骤，还必须处理指针，并且担心内存泄露！
And say you get through the steps described above, you still have to deal with Pointers and worry about memory leaks!
显示在列表1中的代码展示了一个内存渗漏和一个不断摆动的指针。
The code shown in Listing 1 shows both a memory leak and a dangling pointer.
在非垃圾收集语言中需要避免两个主要的内存管理危险：内存泄漏和悬空指针。
There are two major memory-management hazards to avoid in non-garbage-collected languages: memory leaks and dangling Pointers.
悬空指针可能发生在以微妙方式使用内存的代码中。
Dangling Pointers are likely to arise in code, which USES memory in subtle ways.
在对指针赋值前，请确保内存位置不会变为孤立的。
Before assigning the Pointers, make sure memory locations are not becoming orphaned.
垃圾收集器可能错误地收回某些存储，当引用这些存储时，似乎包含到尚未初始化内存的指针。
The garbage collector may incorrectly reclaim some storage that, when referenced, appears to contain pointers to uninitialized memory.
在对指针赋值前，要确保没有内存位置会变为孤立的。
Before assigning the Pointers, make sure no memory locations will become orphaned.
您可能会忘了跟踪所有指针（指向这些内存位置），并且某些内存段没有释放，还保持分配给该程序。
You might forget to keep track of all the pointers (pointing to these memory locations), and some of the memory segments are not freed and stay allocated to the program.
相反，如果您的程序在内存中某个位置存在错误(例如，使用了一个错误指针)，那么可以查找最接近该内存地址的源代码行。
Conversely, if your program has a fault (for example, using a bad pointer) at some location in memory, you can look for the source line that is closest to the memory address.
不管“未来”到达与否，开发者为了一个损坏的指针不断的遍历内存，多少是有些愚蠢的事情了。
"The future" or not, it's getting a bit silly for GUI application developers to perpetually be one bad pointer dereference away from scribbling all over their application's memory.
这和需要你猜测某个内存片包含对象指针和一些类似对象指针的随即数据的老式GC系统有鲜明的对比。
This is in contrast with conservative GC systems which requires you to guess whether some piece of memory contains an object pointer or just some random data that resembles an object pointer.
内存管理复杂性的主要原因是别名使用：同一块内存或对象具有多个指针或引用。
A primary contributor to the complexity of memory management is aliasing: having more than one copy of a pointer or reference to the same block of memory or object.
导致内存破坏的指针操作类型。
dxferp：指向数据传输时长度至少为dxfer_len字节的用户内存的指针。
Dxferp: a pointer to user memory of at least dxfer_len bytes in length for data transfer.
虚拟内存区域（VMA）指针要作为第一个参数，然后是四个常用的参数（start，end，size和protection标记）。
The virtual memory area (VMA) pointer needs to be added in as the first parameter followed by the usual four parameters (start, end, size, and protection flags).
这个系统调用需要shm_open返回的文件描述符，它返回指向内存的指针。
This system call requires the file descriptor from shm_open and returns a pointer to memory.
下一行代码，C3，获取 eax中的指针并将其存储回内存位置为 049388C8的实例引用。
The next line, C3, takes the pointer in eax and stores it back into the instance reference at memory location 049388C8.
先前的例子是关注支持namestr指针本身的内存；因此这个被关注区域是由 &namestr 提供的。
The earlier example was watching the memory that held the namestr pointer itself; therefore, the address of the watched area is given by &namestr.
先前的例子是关注支持namestr指针本身的内存；因此这个被关注区域是由 &namestr 提供的。
The earlier example was watching the memory that held the namestr pointer itself; therefore, the address of the watched area is given by &namestr.
应用推荐