Databases
StackOverflow2013
Postsdbo
POvalgrind memory leak errors when using pthread_create
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POvalgrind memory leak errors when using pthread_create
    primarykey
    data
    text
    <p>I'm writing a program using the pthread library. When i run my program with the command valgrind --leak-check=full, i get the following errors description: </p> <pre><code>==11784== ==11784== **HEAP SUMMARY:** ==11784== in use at exit: 4,952 bytes in 18 blocks ==11784== total heap usage: 1,059 allocs, 1,041 frees, 51,864 bytes allocated ==11784== ==11784== **288 bytes** in 1 blocks are possibly lost in loss record 2 of 3 ==11784== at 0x4C2380C: calloc (vg_replace_malloc.c:467) ==11784== by 0x4010D2E: _dl_allocate_tls (dl-tls.c:300) ==11784== by 0x55DC218: **pthread_create**@@GLIBC_2.2.5 (allocatestack.c:570) ==11784== by 0x401BC0: initdevice(char*) (in /a/fr-01/vol/home/stud/lim/workspace /Ex3/l) ==11784== by 0x406D05: main (in /a/fr-01/vol/home/stud/lim/workspace/Ex3/l) ==11784== ==11784== **4,608 bytes** in 16 blocks are possibly lost in loss record 3 of 3 ==11784== at 0x4C2380C: calloc (vg_replace_malloc.c:467) ==11784== by 0x4010D2E: _dl_allocate_tls (dl-tls.c:300) ==11784== by 0x55DC218: **pthread_create**@@GLIBC_2.2.5 (allocatestack.c:570) ==11784== by 0x40268F: write2device(char*, int) (in /a/fr-01/vol/home/stud/lim/workspace/Ex3/l) ==11784== by 0x406D7B: main (in /a/fr-01/vol/home/stud/lim/workspace/Ex3/l) ==11784== ==11784== **LEAK SUMMARY:** ==11784== definitely lost: 0 bytes in 0 blocks ==11784== indirectly lost: 0 bytes in 0 blocks ==11784== possibly lost: 4,896 bytes in 17 blocks ==11784== still reachable: 56 bytes in 1 blocks ==11784== suppressed: 0 bytes in 0 blocks ==11784== Reachable blocks (those to which a pointer was found) are not shown. ==11784== To see them, rerun with: --leak-check=full --show-reachable=yes ==11784== ==11784== For counts of detected and suppressed errors, rerun with: -v ==11784== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 4 from 4) </code></pre> <hr> <p>Every time i call pthread_create, with a certain function - i call the function pthread_exit in the end of the function. So, after verifying this is not the problem, what could be the problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIharob Al Asimi
    1. USlim
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo did you try to write a program that just do pthread_create/pthread_exit (+join) and run it under valgrind?
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. USHa.
    2. COtry running it with "--leak-check=full --show-reachable=yes". A guess is that structures that are duplicated might not get deleted. But without code to test it myself I can't say much.
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. USRonny Brendel
    3. COare you joining your threads with `pthread_join`? otherwise a leak is to be expected.
      singulars
      1. POvalgrind memory leak errors when using pthread_create
      1. USHasturkun
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload