为什么一个简单的SDL程序会报告Valgrind中的内存泄漏?

Why does a simple SDL program report memory leaks in Valgrind?

本文关键字：报告 Valgrind 泄漏 内存 程序 SDL 简单 一个 为什么      更新时间：2023-10-16

这个程序:

#include <iostream>
#include <SDL2/SDL.h>
/*
 * Lesson 0: Test to make sure SDL is setup properly
 */
int main(int argc, char** argv){
    if (SDL_Init(SDL_INIT_EVERYTHING) != 0){
        std::cout << "SDL_Init Error: " << SDL_GetError() << std::endl;
        return 1;
    }
    SDL_Quit();
    return 0;
}
使用g++ -o main main.cpp -lSDL2; valgrind ./main编译的

产生以下输出:

==21646== HEAP SUMMARY:
==21646==     in use at exit: 108,320 bytes in 582 blocks
==21646==   total heap usage: 16,412 allocs, 15,830 frees, 106,043,200 bytes allocated
==21646== 
==21646== LEAK SUMMARY:
==21646==    definitely lost: 12,058 bytes in 4 blocks
==21646==    indirectly lost: 0 bytes in 0 blocks
==21646==      possibly lost: 0 bytes in 0 blocks
==21646==    still reachable: 96,262 bytes in 578 blocks
==21646==         suppressed: 0 bytes in 0 blocks

这是我应该担心的事情吗?如果是这样，我如何知道我的代码中的误报和实际错误之间的区别?

摘自此stackoverflow答案

在您的具体情况下，我会运行带有标志--leak-check=full --track-origins=yes --show-reachable=yes的valgrind，看看泄漏是否真的来自SDL

相关文章：