08-07-2008
In case you misunderstood me I was talking about calling pthread_detach() with the threadid as its argument in the function main() instead of in function cliente().
If calling pthead_self() inside the function main() then its argument would be the calling id of the initial thread instead of each new thread that is created.
10 More Discussions You Might Find Interesting
1. Programming
Hi
i was trying to compile one of my project source file which is neary 2MB large.
i couldnt compile it, instead getting an error like "insufficient virtual memory"
how come i get away with this problem ,please suggest.
thanks (1 Reply)
Discussion started by: Raom
1 Replies
2. Programming
hi
i have a code:
I found that after exiting from child thread memory isn't freed. I commented everything which is "some actions" here, so thread's function contains only two lines. But it doesn't help.
What do I do wrong?
Thanks a lot (3 Replies)
Discussion started by: sery0ga
3 Replies
3. Programming
Hi all!
I am implementing an http server in c++ using the posix thread, but i am having a memory leak and i cannot find the reason.
I have already commented out the section that initializes the threads and i found out, the problem is when i initialize/run the threads.
In the threads i have... (1 Reply)
Discussion started by: laurovalente
1 Replies
4. UNIX for Advanced & Expert Users
hi
I had to create a shared memory segment which allows the creation of 8 child processes each with 1024 bytes and contains a common buffer area of 2096bytes.
i was able to create the shared memory with shm_open() followed by ftruncate() and mmap() system calls.
but for the shared buffer, i... (3 Replies)
Discussion started by: pretty
3 Replies
5. AIX
Hi,
Would any one be so kind to explain me :
are ulimits defined for each user seperately ? When ?
Specialy what is the impact of :
max locked memory
and
virtual memory
on performance of applications for a user.
Many thanks.
PS :
this is what I can see in MAN :
ulimit ]
... (5 Replies)
Discussion started by: big123456
5 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
Does anyone know what the best commands in the UNIX command line are for obtaining this info:
current CPU usage
memory usage
virtual memory usage
preferably with date and time parameters too?
thanks
ocelot (4 Replies)
Discussion started by: ocelot
4 Replies
7. UNIX for Advanced & Expert Users
i am creating threads in my program using the POSIX interface.
when the thread starts executing i run out of memory and get a core dump.
i have tried to increase the threads stack size using pthread_attr_setstacksize, but of no use since i guess the dynamic memory is allocated on the heap and... (1 Reply)
Discussion started by: aniketkadu2002
1 Replies
8. Programming
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
9. Programming
Hi,
I wanted to know whether the POSIX message queues are statically allocated memory by the kernel based on the parameters specified in the open or as and when we send messages, memory are allocated?
Does the kernel reserve the specified memory for the message queue irrespective of whether... (1 Reply)
Discussion started by: sumtata
1 Replies
10. Solaris
Hi
I have a problem with Virtual Memory on one local zone (myzone1):
//from local zone (myzone1)
swap -s
total: 22888544k bytes allocated + 0k reserved = 22888544k used, 3325856k available
swap -l
swapfile dev swaplo blocks free
/dev/swap ... (0 Replies)
Discussion started by: primo102
0 Replies
LEARN ABOUT DEBIAN
iv_thread_create
iv_thread(3) ivykis programmer's manual iv_thread(3)
NAME
iv_thread_create, iv_thread_set_debug_state - ivykis thread convenience functions
SYNOPSIS
#include <iv_thread.h>
int iv_thread_create(char *name, void (*start_routine)(void *), void *arg);
void iv_thread_set_debug_state(int state);
DESCRIPTION
iv_thread_create is a wrapper around pthread_create(3) which will maintain an ivykis main loop reference in the calling thread (which must
be an ivykis(3) thread, i.e. have had iv_init(3) called in it) for as long as the created thread is alive.
Maintaining a reference on the calling thread's ivykis event loop makes sure that the calling thread will not return from its ivykis main
loop before the created thread exits, as that could cause cleanup still happening in the created thread to be interrupted when the calling
thread subsequently calls exit(3).
The created thread need not be an ivykis thread.
Enabling debugging by calling iv_thread_set_debug with a nonzero argument will print a debug message to standard error whenever a thread is
created via iv_thread_create, whenever a thread so created terminates normally by returning from its start_routine, self-terminates by
calling pthread_exit(3), or is successfully canceled by pthread_cancel(3), and whenever destruction of such a thread is signaled back to
the calling thread.
For inter-thread signaling, iv_thread uses iv_event(3).
SEE ALSO
ivykis(3), iv_event(3), exit(3), pthread_cancel(3), pthread_create(3), pthread_exit(3)
ivykis 2010-09-13 iv_thread(3)