我有一个ncurses程序，用setterm设置两个SCREEN。 我相信我没有正确地完成它们，因为我得到了一堆valgrind错误（见下文）。 知道什么是错的吗？ 谢谢！
#include <ncurses.h>
SCREEN * sstderr;
SCREEN * sstdout;
int main() {
sstderr = newterm(NULL, stderr, NULL);
noecho();
sstdout = newterm(NULL, stdout, stdin);
set_term(sstdout);
mvaddstr(0, 0, "algo\n");
clrtobot();
getch();
refresh();
set_term(sstdout);
endwin();
set_term(sstderr);
endwin();
return 0;
}
Valgrind报道：
==10283== Memcheck, a memory error detector
==10283== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10283== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==10283== Command: ./a.out
==10283== Parent PID: 669
==10283==
==10283==
==10283== HEAP SUMMARY:
==10283== in use at exit: 1,225,551 bytes in 313 blocks
==10283== total heap usage: 328 allocs, 15 frees, 1,242,329 bytes allocated
==10283==
==10283== 296 bytes in 1 blocks are possibly lost in loss record 27 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B88D: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBC5: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 296 bytes in 1 blocks are possibly lost in loss record 28 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B88D: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBEA: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 296 bytes in 1 blocks are possibly lost in loss record 29 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B88D: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FD50: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 704 bytes in 1 blocks are possibly lost in loss record 37 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B8AF: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBC5: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 704 bytes in 1 blocks are possibly lost in loss record 38 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B8AF: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBEA: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 704 bytes in 1 blocks are possibly lost in loss record 39 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5B8AF: _nc_makenew_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5BB2D: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FD50: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 197,120 bytes in 44 blocks are possibly lost in loss record 53 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5BB83: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBC5: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 197,120 bytes in 44 blocks are possibly lost in loss record 54 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5BB83: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FBEA: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== 197,120 bytes in 44 blocks are possibly lost in loss record 55 of 55
==10283== at 0x4C2CA40: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10283== by 0x4E5BB83: newwin_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5FD50: _nc_setupscreen_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x4E5B17E: newterm_sp (in /usr/lib/libncursesw.so.6.0)
==10283== by 0x400932: main (in /home/mongo/a.out)
==10283==
==10283== LEAK SUMMARY:
==10283== definitely lost: 0 bytes in 0 blocks
==10283== indirectly lost: 0 bytes in 0 blocks
==10283== possibly lost: 594,360 bytes in 138 blocks
==10283== still reachable: 631,191 bytes in 175 blocks
==10283== suppressed: 0 bytes in 0 blocks
==10283== Reachable blocks (those to which a pointer was found) are not shown.
==10283== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==10283==
==10283== For counts of detected and suppressed errors, rerun with: -v
==10283== ERROR SUMMARY: 9 errors from 9 contexts (suppressed: 0 from 0)
答案 0 :(得分：3)
它是FAQ：
也许您使用了dmalloc或valgrind等工具来检查内存泄漏。它通常会报告仍在使用的大量内存。这很正常。
ncurses configure脚本有一个选项--disable-leaks，您可以使用它来继续分析。如果可能的话，它告诉ncurses释放内存。但是，大多数使用中的内存都是永久性的＆＃34;。
任何curses实现都不能释放与屏幕关联的内存，因为（即使在调用endwin（）之后），它必须可用于下一次调用refresh（）。出于性能原因，还有大量的内存。这使得很难分析curses应用程序的内存泄漏。要解决这个问题，请构建一个ncurses库的调试版本，它可以释放它可以使用的那些块，并提供_nc_free_and_exit（）函数以在退出时释放余数。 ncurses实用程序和测试程序使用此功能，例如，通过ExitProgram（）宏。
跟随评论：这里的问题是，根据编译时配置，ncurses维护每个屏幕的窗口列表或全局窗口列表（跨所有屏幕）。在后者中，它在创建新屏幕时丢弃了列表。 Fixed now：
20170325
+ fix a memory leak in the window-list when creating multiple screens
(reports by Andres Martinelli, Debian #783486).