• 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

  • 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,它会导致渗漏不断摆动的指针。

    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
- 来自原声例句
小调查
请问您想要如何调整此模块?

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

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