全部

1·Listing 1. Code with memory leak and dangling pointer (mem_errors.c).

列表1 .带有一个内存渗漏和一个不断摆动的指针的代码(mem_errors . c)。

2·The code shown in Listing 1 shows both a memory leak and a dangling pointer.

显示在列表1中的代码展示了一个内存渗漏和一个不断摆动的指针。

3·Using an invalidated iterator is undefined, and likely to lead to the same kinds of problems as using a dangling pointer.

使用无效迭代器是没有定义的，可能会导致与悬垂指针相同的问题。

4·In main, after returning from foo , namestr is actually a dangling pointer, because foo has freed that memory before returning.

在main中，当从foo返回后，namestr实际上时一个摆动的指针，因为foo已经在返回前释放了那个内存。

5·However, it is the interaction of these two functions and using a global pointer variable called namestr that causes both the leak and the dangling pointer.

然而，它是这两个函数的相互作用，利用一个全球性的指针变量叫做namestr，它会导致渗漏和不断摆动的指针。

6·To avoid dangling Pointers (the dangerous situation where a block of memory is freed but a pointer still references it), you must delete the object only after the last reference is released.

为了避免悬空指针(一种危险的情况，即一块内存已经被释放了，而一个指针还在引用它)，必须在最后的引用释放之后才删除对象。

7·The first bug pattern relating to null-pointer exceptions that we'll explore is one that I call the Dangling Composite pattern.

我们将探讨的第一个关于空指针异常的错误类型，是一个我称之为悬挂复合类型的错误类型。