<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Multumesc de hint.<div class="">Intradevar, problema era ca nu asteptam in toate scenariile, dupa toate threadurile.</div><div class=""><br class=""></div><div class="">Acum vad ca trec toate testele de memorie pe vmchecker.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Doar pe masina virtuala, cand rulez valgrind peste acel test 16 (15 pe vm), logurile de sistem indica out-of-memory:</div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Apr 24 10:11:14 vagrant kernel: [109075.123564] Out of memory: Kill process 11250 (memcheck-amd64-) score 866 or sacrifice child</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Apr 24 10:11:14 vagrant kernel: [109075.124387] Killed process 11250 (memcheck-amd64-) total-vm:4736696kB, anon-rss:309400kB, file-rss:0kB, shmem-rss:0kB</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Apr 24 10:11:14 vagrant kernel: [109075.153180] oom_reaper: reaped process 11250 (memcheck-amd64-), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB</span></div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 23 Apr 2019, at 22:27, Razvan Crainea <<a href="mailto:razvan.crainea@gmail.com" class="">razvan.crainea@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Salut, Rareș!<br class=""><br class="">Cel mai probabil nu aștepți toate thread-urile, de acolo apare leak-ul.<br class="">Legat de faptul că că procesul este omorât, poți verifica log-urile de<br class="">sistem să te asiguri că nu este un crash?<br class=""><br class="">Numai bine,<br class="">Răzvan<br class=""><br class="">On Tue, Apr 23, 2019 at 9:10 PM Rares Folea via so <<a href="mailto:so@cursuri.cs.pub.ro" class="">so@cursuri.cs.pub.ro</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">Buna seara!<br class=""><br class="">Ma confrunt cu urmatoarele probleme referitoare la testele de memorie:<br class=""><br class="">La rularea pe masina virtuala cu valgrind a testelor 15 si 19 (14 si 18 pe vmchecker), obtin 2 erori similare:<br class=""><br class="">==4684== 288 bytes in 1 blocks are possibly lost in loss record 2 of 2<br class="">==4684== at 0x4C3204A: calloc (vg_replace_malloc.c:762)<br class="">==4684== by 0x40134A6: allocate_dtv (dl-tls.c:286)<br class="">==4684== by 0x40134A6: _dl_allocate_tls (dl-tls.c:530)<br class="">==4684== by 0x5049227: allocate_stack (allocatestack.c:627)<br class="">==4684== by 0x5049227: pthread_create@@GLIBC_2.2.5 (pthread_create.c:644)<br class="">==4684== by 0x4E3E65B: so_fork (in /home/student/l3-so-assignments/4-scheduler/checker-lin/libscheduler.so)<br class="">==4684== by 0x10ABDE: test_sched_handler_15 (test_exec.c:282)<br class="">==4684== by 0x4E3E47E: start_thread (in /home/student/l3-so-assignments/4-scheduler/checker-lin/libscheduler.so)<br class="">==4684== by 0x50486DA: start_thread (pthread_create.c:463)<br class="">==4684== by 0x538188E: clone (clone.S:95)<br class=""><br class="">==4684== possibly lost: 576 bytes in 2 blocks<br class=""><br class="">==4684== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)<br class=""><br class="">Nu reusesc sa-mi dau seama de la ce ar putea fi cele doua erori si de ce se manifesta doar la aceste doua teste.<br class="">Mentionez ca astept terminarea thread-urilor cu pthread_join, care ar trebui sa efectueze eliberarea resurselor din structura pthread_t.<br class="">In plus, la testul 16 (15 vmchecker), se pare ca valgrind ocupa mult prea multa memorie locala, iar ca urmare este omorat.<br class=""><br class="">student@vagrant:~/l3-so-assignments/4-scheduler/checker-lin$ LD_LIBRARY_PATH=. valgrind --tool=memcheck --track-origins=yes --leak-check=full _test/run_test 16<br class="">==4693== Memcheck, a memory error detector<br class="">==4693== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.<br class="">==4693== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info<br class="">==4693== Command: _test/run_test 16<br class="">==4693==<br class="">Killed<br class=""><br class=""><br class="">Multumesc<br class="">_______________________________________________<br class=""><a href="http://ocw.cs.pub.ro/courses/so/info/lista-discutii" class="">http://ocw.cs.pub.ro/courses/so/info/lista-discutii</a><br class=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Răzvan Crainea<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>