Sponsored Content
Top Forums UNIX for Advanced & Expert Users Memory leak while using pthread_cancel() Post 302315331 by kcr on Tuesday 12th of May 2009 05:30:57 AM
Old 05-12-2009
Memory leak while using pthread_cancel()

I tried to execute a sample pthread program to cancel a newly created one using pthread_cancel(). but using valgrind on my code shows some memory leak.
My Code:
#include "iostream"
#include "unistd.h"
#include "pthread.h"
#include "signal.h"
using namespace std;
void handler(int);
void* testFun(void *arg)
{
cout<<"Iam child process \n";
sleep(2);
pthread_exit(NULL);
}
int main()
{
pthread_t threads;
int i=5;
int *p=&i;
pthread_create(&threads, NULL, testFun,(void *)&i);
cout<<"Main thread cancelling the child\n";
pthread_cancel(threads);
cout<<"waiting for child\n";
pthread_join(threads,(void**)&p);
cout<<"main thread exiting\n bye Smilie";
}


Valgrind output:
==16040== Memcheck, a memory error detector.
==16040== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==16040== Using LibVEX rev 1732, a library for dynamic binary translation.
==16040== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==16040== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==16040== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==16040== For more details, rerun with: -v
==16040==
Iam child process
Main thread cancelling the child
waiting for child
main thread exiting
bye Smilie==16040==
==16040== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
==16040== malloc/free: in use at exit: 28 bytes in 1 blocks.
==16040== malloc/free: 2 allocs, 1 frees, 172 bytes allocated.
==16040== For counts of detected errors, rerun with: -v
==16040== searching for pointers to 1 not-freed blocks.
==16040== checked 104,232 bytes.
==16040==
==16040== 28 bytes in 1 blocks are still reachable in loss record 1 of 1
==16040== at 0x4022525: malloc (vg_replace_malloc.c:149)
==16040== by 0x400CDD2: _dl_map_object_deps (in /lib/ld-2.7.so)
==16040== by 0x4011ECC: dl_open_worker (in /lib/ld-2.7.so)
==16040== by 0x400E1B5: _dl_catch_error (in /lib/ld-2.7.so)
==16040== by 0x4011851: _dl_open (in /lib/ld-2.7.so)
==16040== by 0x42835D1: do_dlopen (in /lib/libc-2.7.so)
==16040== by 0x400E1B5: _dl_catch_error (in /lib/ld-2.7.so)
==16040== by 0x4283784: __libc_dlopen_mode (in /lib/libc-2.7.so)
==16040== by 0x416D206: pthread_cancel_init (in /lib/libpthread-2.7.so)
==16040== by 0x4169648: pthread_cancel (in /lib/libpthread-2.7.so)
==16040== by 0x80487F4: main (test.cpp:36)
==16040==
==16040== LEAK SUMMARY:
==16040== definitely lost: 0 bytes in 0 blocks.
==16040== possibly lost: 0 bytes in 0 blocks.
==16040== still reachable: 28 bytes in 1 blocks.
==16040== suppressed: 0 bytes in 0 blocks.
I dont know where these 28 bytes are lost.Smilie
how to rectify this leak????
thanks in advance
 

9 More Discussions You Might Find Interesting

1. Programming

about virtual memory and memory leak

Hi, First of all I appreciate this group very much for its informative discussions and posts. Here is my question. I have one process whose virtual memory size increases linearly from 6MB to 12MB in 20 minutes. Does that mean my process has memory leaks? In what cases does the... (4 Replies)
Discussion started by: shriashishpatil
4 Replies

2. Programming

Memory leak of fork()

Today, I wrote a test code for fork/execvp/waitpid. In the parent process, it fork 100 child processes which only execute "date" to print the current datetime. When any child process die, the parent process will receive a SIGCHLD signal. Then, the parent process will re-fork-execvp the child... (7 Replies)
Discussion started by: whererush
7 Replies

3. Programming

Memory LEAK with pthreads

I have this code... #include <stdio.h> #include <iostream> #include <pthread.h> static void* cliente(void *datos); int main() { pthread_attr_t tattr; int ret; size_t size = PTHREAD_STACK_MIN + 0x0100; ret = pthread_attr_init(&tattr); ret =... (8 Replies)
Discussion started by: JEscola
8 Replies

4. UNIX for Advanced & Expert Users

Memory leak in pthread

helo frnds, I am using RHEL5 and C lang for development. I am getting some memory leak problem in pthread. I hav developed a program which creates two threads for listening purpose on two diff ports. both the child threads are doing same job but on diff port no. I am using... (4 Replies)
Discussion started by: mindTeaser
4 Replies

5. IP Networking

memory leak?

Hi All, my client server application can work in two modes: 1) one direction - only client sends msgs to server 2) two directions - server gives 'answers' to client. when program run in the first mode it looks OK, but when server answers to client than client's application exit its... (2 Replies)
Discussion started by: lenna
2 Replies

6. Programming

memory leak problem

hi all Can any one plz explain me about memory leak problem Thankx (5 Replies)
Discussion started by: sonali
5 Replies

7. Programming

Memory Leak

Hi, I am trying a database server which keeps a B+ plus tree structure and works on it. I am trying to find the memory used/leak while executing this process. I check the memory leak by using ps uax command. When i execute a delete query i am sure that my code frees up the existing... (9 Replies)
Discussion started by: kumaran_5555
9 Replies

8. Red Hat

Memory leak

Hi all I am using RED HAT 5.4, and i am getting memory uses problem. when i use "sync;echo 3 > /proc/sys/vm/drop_cache" command the memory will release after 2,3 hour memory show 95%. pls suggest right way. thanks (37 Replies)
Discussion started by: reply.ravi
37 Replies

9. Web Development

Finding Cause of Memory Leak

Hi We have just got a dedicated server with Fasthosts, O/S is Linux CentOS 6 64 bit. It was a fresh install and I have just moved one WordPress site onto there. The problem is we seem to be getting a memory leak (that's what Fasthosts said) and the database (I think) keeps crashing, so we... (3 Replies)
Discussion started by: Pokeyzx
3 Replies
PTHREAD_CLEANUP_PUSH_DEFER_NP(3)			     Linux Programmer's Manual				  PTHREAD_CLEANUP_PUSH_DEFER_NP(3)

NAME
pthread_cleanup_push_defer_np, pthread_cleanup_pop_restore_np - push and pop thread cancellation clean-up handlers while saving cancelabil- ity type SYNOPSIS
#include <pthread.h> void pthread_cleanup_push_defer_np(void (*routine)(void *), void *arg); void pthread_cleanup_pop_restore_np(int execute); Compile and link with -pthread. DESCRIPTION
These functions are the same as pthread_cleanup_push(3) and pthread_cleanup_pop(3), except for the differences noted on this page. Like pthread_cleanup_push(3), pthread_cleanup_push_defer_np() pushes routine onto the thread's stack of cancellation clean-up handlers. In addition, it also saves the thread's current cancelability type, and sets the cancelability type to "deferred" (see pthread_setcancel- type(3)); this ensures that cancellation clean-up will occur even if the thread's cancelability type was "asynchronous" before the call. Like pthread_cleanup_pop(3), pthread_cleanup_pop_restore_np() pops the top-most clean-up handler from the thread's stack of cancellation clean-up handlers. In addition, it restores the thread's cancelability type to its value at the time of the matching pthread_cleanup_push_defer_np(). The caller must ensure that calls to these functions are paired within the same function, and at the same lexical nesting level. Other restrictions apply, as described in pthread_cleanup_push(3). This sequence of calls: pthread_cleanup_push_defer_np(routine, arg); pthread_cleanup_pop_restore_np(execute); is equivalent to (but shorter and more efficient than): int oldtype; pthread_cleanup_push(routine, arg); pthread_setcanceltype(PTHREAD_CANCEL_DEFERRED, &oldtype); ... pthread_setcanceltype(oldtype, NULL); pthread_cleanup_pop(execute); CONFORMING TO
These functions are nonstandard GNU extensions; hence the suffix "_np" (nonportable) in the names. SEE ALSO
pthread_cancel(3), pthread_cleanup_push(3), pthread_setcancelstate(3), pthread_testcancel(3), pthreads(7) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-12-04 PTHREAD_CLEANUP_PUSH_DEFER_NP(3)
All times are GMT -4. The time now is 04:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy