[Valgrind-users] stack trace and pthreads

[<Voj...@se...>]

Hello,

if I try to run memcheck on the following sample program I see only one-line stack trace for an error in thread created with pthread_create. The error in the main thread is shown well. Did I miss anything or is it a bug?

---------------------------------------------------------------------------------------------------------
the program:

#include <unistd.h>     /* Symbolic Constants */
#include <sys/types.h>  /* Primitive System Data Types */ 
#include <errno.h>      /* Errors */
#include <stdio.h>      /* Input/Output */
#include <stdlib.h>     /* General Utilities */
#include <pthread.h>    /* POSIX Threads */

//memory leak
void do_leak()
{
	int* ptr = new int[10];
}

//mismatched new[]/delete
void do_mismatch()
{
	int* ptr = new int[10];
	delete ptr;
}

//run in the new thread
void* print_message_function ( void *ptr )
{
    printf("new thread says Hello! \n");

    //do_leak();
    do_mismatch();
    
    pthread_exit(0);
    return NULL;
}

int main()
{
    pthread_t thread1;
    pthread_create (&thread1, NULL, &print_message_function, NULL);

    do_leak();
    //do_mismatch();

    pthread_join(thread1, NULL);  
    exit(0);
} 

---------------------------------------------------------------------------------------------------------
the output after running: valgrind --leak-check=full ./a.out

==21295== Memcheck, a memory error detector.
==21295== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==21295== Using LibVEX rev 1804, a library for dynamic binary translation.
==21295== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==21295== Using valgrind-3.3.0, a dynamic binary instrumentation framework.
==21295== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==21295== For more details, rerun with: -v
==21295== 
==21295== My PID = 21295, parent PID = 20915.  Prog and args are:
==21295==    ./a.out
==21295== 
==21295== Thread 2:
==21295== Mismatched free() / delete / delete []
==21295==    at 0x4023779: operator delete(void*) (vg_replace_malloc.c:342)
==21295==  Address 0x4a81138 is 0 bytes inside a block of size 40 alloc'd
==21295==    at 0x4023079: operator new[](unsigned) (vg_replace_malloc.c:268)
==21295== 
==21295== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 3 from 1)
==21295== malloc/free: in use at exit: 68 bytes in 2 blocks.
==21295== malloc/free: 4 allocs, 2 frees, 244 bytes allocated.
==21295== For counts of detected errors, rerun with: -v
==21295== searching for pointers to 2 not-freed blocks.
==21295== checked 134,892 bytes.
==21295== 
==21295== Thread 1:
==21295== 
==21295== 40 bytes in 1 blocks are definitely lost in loss record 2 of 2
==21295==    at 0x4023079: operator new[](unsigned) (vg_replace_malloc.c:268)
==21295==    by 0x804866B: do_leak() (thread-ex.cpp:11)
==21295==    by 0x80486E9: main (thread-ex.cpp:38)
==21295== 
==21295== LEAK SUMMARY:
==21295==    definitely lost: 40 bytes in 1 blocks.
==21295==      possibly lost: 0 bytes in 0 blocks.
==21295==    still reachable: 28 bytes in 1 blocks.
==21295==         suppressed: 0 bytes in 0 blocks.
==21295== Reachable blocks (those to which a pointer was found) are not shown.
==21295== To see them, rerun with: --leak-check=full --show-reachable=yes 

---------------------------------------------------------------------------------------------------------
Vojtech