Sponsored Content
Full Discussion: Memory LEAK with pthreads
Top Forums Programming Memory LEAK with pthreads Post 302314106 by JEscola on Thursday 7th of May 2009 11:25:15 AM
Old 05-07-2009
Running the source before creating

0000000000400000 4K r-x-- /home/CSources/samples/thread1
0000000000600000 4K rw--- /home/CSources/samples/thread1
0000003602200000 112K r-x-- /lib64/ld-2.5.so
000000360241b000 4K r---- /lib64/ld-2.5.so
000000360241c000 4K rw--- /lib64/ld-2.5.so
0000003603200000 1328K r-x-- /lib64/libc-2.5.so
000000360334c000 2048K ----- /lib64/libc-2.5.so
000000360354c000 16K r---- /lib64/libc-2.5.so
0000003603550000 4K rw--- /lib64/libc-2.5.so
0000003603551000 20K rw--- [ anon ]
0000003603600000 520K r-x-- /lib64/libm-2.5.so
0000003603682000 2044K ----- /lib64/libm-2.5.so
0000003603881000 4K r---- /lib64/libm-2.5.so
0000003603882000 4K rw--- /lib64/libm-2.5.so
0000003603e00000 88K r-x-- /lib64/libpthread-2.5.so
0000003603e16000 2044K ----- /lib64/libpthread-2.5.so
0000003604015000 4K r---- /lib64/libpthread-2.5.so
0000003604016000 4K rw--- /lib64/libpthread-2.5.so
0000003604017000 16K rw--- [ anon ]
000000360dc00000 52K r-x-- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360dc0d000 2048K ----- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360de0d000 4K rw--- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360f400000 920K r-x-- /usr/lib64/libstdc++.so.6.0.8
000000360f4e6000 2044K ----- /usr/lib64/libstdc++.so.6.0.8
000000360f6e5000 24K r---- /usr/lib64/libstdc++.so.6.0.8
000000360f6eb000 12K rw--- /usr/lib64/libstdc++.so.6.0.8
000000360f6ee000 72K rw--- [ anon ]
00002b292036a000 8K rw--- [ anon ]
00002b2920389000 16K rw--- [ anon ]
00007fff8a72a000 84K rw--- [ stack ]
ffffffffff600000 8192K ----- [ anon ]
total 21748K

After....

0000000000400000 4K r-x-- /home/CSources/samples/thread1
0000000000600000 4K rw--- /home/CSources/samples/thread1
0000000014a24000 132K rw--- [ anon ]
0000000041ea8000 4K ----- [ anon ]
0000000041ea9000 10240K rw--- [ anon ]
00000000428a9000 4K ----- [ anon ]
00000000428aa000 10240K rw--- [ anon ]
00000000432aa000 4K ----- [ anon ]
00000000432ab000 10240K rw--- [ anon ]
0000000043cab000 4K ----- [ anon ]
0000000043cac000 10240K rw--- [ anon ]
0000003602200000 112K r-x-- /lib64/ld-2.5.so
000000360241b000 4K r---- /lib64/ld-2.5.so
000000360241c000 4K rw--- /lib64/ld-2.5.so
0000003603200000 1328K r-x-- /lib64/libc-2.5.so
000000360334c000 2048K ----- /lib64/libc-2.5.so
000000360354c000 16K r---- /lib64/libc-2.5.so
0000003603550000 4K rw--- /lib64/libc-2.5.so
0000003603551000 20K rw--- [ anon ]
0000003603600000 520K r-x-- /lib64/libm-2.5.so
0000003603682000 2044K ----- /lib64/libm-2.5.so
0000003603881000 4K r---- /lib64/libm-2.5.so
0000003603882000 4K rw--- /lib64/libm-2.5.so
0000003603e00000 88K r-x-- /lib64/libpthread-2.5.so
0000003603e16000 2044K ----- /lib64/libpthread-2.5.so
0000003604015000 4K r---- /lib64/libpthread-2.5.so
0000003604016000 4K rw--- /lib64/libpthread-2.5.so
0000003604017000 16K rw--- [ anon ]
000000360dc00000 52K r-x-- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360dc0d000 2048K ----- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360de0d000 4K rw--- /lib64/libgcc_s-4.1.2-20080825.so.1
000000360f400000 920K r-x-- /usr/lib64/libstdc++.so.6.0.8
000000360f4e6000 2044K ----- /usr/lib64/libstdc++.so.6.0.8
000000360f6e5000 24K r---- /usr/lib64/libstdc++.so.6.0.8
000000360f6eb000 12K rw--- /usr/lib64/libstdc++.so.6.0.8
000000360f6ee000 72K rw--- [ anon ]
00002aaaaae7f000 4K rw--- [ anon ]
00002aeeccfe5000 8K rw--- [ anon ]
00002aeecd004000 16K rw--- [ anon ]
00007fffddab0000 84K rw--- [ stack ]
ffffffffff600000 8192K ----- [ anon ]
total 62860K
 

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

Problem with POSIX pthreads and virtual memory

Hi, i have this code... in order to test my problem... #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 =... (8 Replies)
Discussion started by: JEscola
8 Replies

3. UNIX for Advanced & Expert Users

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*... (4 Replies)
Discussion started by: kcr
4 Replies

4. UNIX for Advanced & Expert Users

Need to create a memory leak

Hi. This might be a strange request, but does anyone have any idea on a simple shell script that would use more and more memory as it ran? Like a purposeful leak. I want to test the behaviour of an already running program when the machine runs out of memory. Thanks! (4 Replies)
Discussion started by: rebelbuttmunch
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. Programming

Help regarding memory leak in this C program

I have written this code in C which reads a very large collection of text files and does some processing. The problem with this code is that there are memory leaks which I am not able to figure out as to where the problem is. When I run this code, and see the memory usage using top command, then I... (7 Replies)
Discussion started by: shoaibjameel123
7 Replies
PTHREAD_ATTR_SETDETACHSTATE(3)				     Linux Programmer's Manual				    PTHREAD_ATTR_SETDETACHSTATE(3)

NAME
pthread_attr_setdetachstate, pthread_attr_getdetachstate - set/get detach state attribute in thread attributes object SYNOPSIS
#include <pthread.h> int pthread_attr_setdetachstate(pthread_attr_t *attr, int detachstate); int pthread_attr_getdetachstate(pthread_attr_t *attr, int *detachstate); Compile and link with -pthread. DESCRIPTION
The pthread_attr_setdetachstate() function sets the detach state attribute of the thread attributes object referred to by attr to the value specified in detachstate. The detach state attribute determines whether a thread created using the thread attributes object attr will be created in a joinable or a detached state. The following values may be specified in detachstate: PTHREAD_CREATE_DETACHED Threads that are created using attr will be created in a detached state. PTHREAD_CREATE_JOINABLE Threads that are created using attr will be created in a joinable state. The default setting of the detach state attribute in a newly initialized thread attributes object is PTHREAD_CREATE_JOINABLE. The pthread_attr_getdetachstate() returns the detach state attribute of the thread attributes object attr in the buffer pointed to by detachstate. RETURN VALUE
On success, these functions return 0; on error, they return a nonzero error number. ERRORS
pthread_attr_setdetachstate() can fail with the following error: EINVAL An invalid value was specified in detachstate. CONFORMING TO
POSIX.1-2001. NOTES
See pthread_create(3) for more details on detached and joinable threads. A thread that is created in a joinable state should eventually either be joined using pthread_join(3) or detached using pthread_detach(3); see pthread_create(3). It is an error to specify the thread ID of a thread that was created in a detached state in a later call to pthread_detach(3) or pthread_join(3). EXAMPLE
See pthread_attr_init(3). SEE ALSO
pthread_attr_init(3), pthread_create(3), pthread_detach(3), pthread_join(3), pthreads(7) COLOPHON
This page is part of release 3.44 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 2010-02-03 PTHREAD_ATTR_SETDETACHSTATE(3)
All times are GMT -4. The time now is 12:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy