From 15c337fc02f3a03712148c314949980167e72c54 Mon Sep 17 00:00:00 2001
From: 1Bc <58879458+1Bc@users.noreply.github.com>
Date: Mon, 13 Jul 2026 17:59:33 +0200
Subject: [PATCH] Add Valgrind output for resourceD

Added Valgrind output for memory leak analysis.
---
 homework/resourceD/valgrind-output.txt | 28 ++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/homework/resourceD/valgrind-output.txt b/homework/resourceD/valgrind-output.txt
index e69de29b..fef06147 100644
--- a/homework/resourceD/valgrind-output.txt
+++ b/homework/resourceD/valgrind-output.txt
@@ -0,0 +1,28 @@
+ @phil  valgrind --leak-check=full ./build/resourceD d
+==214534== Memcheck, a memory error detector
+==214534== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
+==214534== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info
+==214534== Command: ./build/resourceD d
+==214534== 
+Using resource. Passed d
+Passed d. d is prohibited.
+==214534== 
+==214534== HEAP SUMMARY:
+==214534==     in use at exit: 73,729 bytes in 2 blocks
+==214534==   total heap usage: 5 allocs, 3 frees, 74,948 bytes allocated
+==214534== 
+==214534== 1 bytes in 1 blocks are definitely lost in loss record 1 of 2
+==214534==    at 0x4960093: operator new(unsigned long) (vg_replace_malloc.c:487)
+==214534==    by 0x40177B1: main (resourceD.cpp:30)
+==214534== 
+==214534== LEAK SUMMARY:
+==214534==    definitely lost: 1 bytes in 1 blocks
+==214534==    indirectly lost: 0 bytes in 0 blocks
+==214534==      possibly lost: 0 bytes in 0 blocks
+==214534==    still reachable: 73,728 bytes in 1 blocks
+==214534==         suppressed: 0 bytes in 0 blocks
+==214534== Reachable blocks (those to which a pointer was found) are not shown.
+==214534== To see them, rerun with: --leak-check=full --show-leak-kinds=all
+==214534== 
+==214534== For lists of detected and suppressed errors, rerun with: -s
+==214534== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)