antirez / antirez/sds

valgrind reports realloc-related memory leaks

オープン
#41 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
C
スター
5.6k
フォーク
510
PR マージ指標
30日以内にマージされた PR はありません

説明

There is something about sdsMakeRoomFor that leaks memory, at least according to valgrind:

```
==31090== HEAP SUMMARY:
==31090== in use at exit: 40 bytes in 2 blocks
==31090== total heap usage: 33 allocs, 31 frees, 526 bytes allocated
==31090==
==31090== 13 bytes in 1 blocks are definitely lost in loss record 1 of 2
==31090== at 0x4C2CE8E: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31090== by 0x401B51: sdsMakeRoomFor (sds.c:160)
==31090== by 0x40132A: main (sds.c:926)
==31090==
==31090== 27 bytes in 1 blocks are definitely lost in loss record 2 of 2
==31090== at 0x4C2CE8E: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31090== by 0x401B51: sdsMakeRoomFor (sds.c:160)
==31090== by 0x401CF0: sdscatlen (sds.c:269)
==31090== by 0x401EFA: sdscatvprintf (sds.c:342)
==31090== by 0x401FA6: sdscatprintf (sds.c:367)
==31090== by 0x4026AE: sdscatrepr (sds.c:602)
==31090== by 0x40126A: main (sds.c:915)
==31090==
==31090== LEAK SUMMARY:
==31090== definitely lost: 40 bytes in 2 blocks
==31090== indirectly lost: 0 bytes in 0 blocks
==31090== possibly lost: 0 bytes in 0 blocks
==31090== still reachable: 0 bytes in 0 blocks
==31090== suppressed: 0 bytes in 0 blocks
```

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。