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

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

    youdao

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

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

    youdao

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

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

    youdao

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

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

    youdao

  • 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.

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

    youdao

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

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

    youdao

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

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

    youdao

$firstVoiceSent
- 来自原声例句
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定