09-29-2005
2. yes, you can.
you can do force convertion. In C, the any convertion is allowed, but you should guarantee the safety.
10 More Discussions You Might Find Interesting
1. Programming
hi all,
can anyone tell me some good site for the mutithreading tutorials, its application, and some code examples.
-sushil (2 Replies)
Discussion started by: shushilmore
2 Replies
2. Programming
Is there anybody has documents about NPTL
I wanna study about it , but can't find the documents....
anyone help appreciate
:) :) :) (1 Reply)
Discussion started by: alan.zhao
1 Replies
3. Programming
pthread_create(&tid, &Attr, A, NULL);
pthread_create(&tid, &Attr, B, NULL);
pthread_create(&tid, &Attr, C, NULL);
A,B,C are the name of the functiont that the thread excute
Hi all !
I want to ask so with these commands ,how the program will excute .
What the way it will do .
Please... (0 Replies)
Discussion started by: iwbasts
0 Replies
4. 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
5. Programming
Hello,
I have created program that run threads one by one, maximum 100. Each thread will process one block of data, and once it`s finished, new thread is created with new block of data....etc
I have array of values to control status of each thread, like this:
array_thread_status=1... (11 Replies)
Discussion started by: orangem
11 Replies
6. Programming
I am facing a strange error while creating posix threads:
Given below are two snippets of code, the first one works whereas the second one gives a garbage value in the output.
Snippet 1
This works:
--------------
int *threadids;
threadids = (int *) malloc (num_threads * sizeof(int));
... (4 Replies)
Discussion started by: kmehta
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 can see a number of header files in the POSIX standard related to TCP/IP based socket programming:
arpa/inet.h
net/if.h
netdb.h
netinet/in.h
netinet/tcp.h
sys/socket.h
Except for socket.h, I am a little confused what's the purpose of so many header files and when to include which.... (3 Replies)
Discussion started by: jaywalker
3 Replies
9. Programming
in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario:
client:Knock Knock
server:who's there
client: Eric
Server:Eric,Welcome.
client:exit
all process terminated
... (1 Reply)
Discussion started by: ouou
1 Replies
10. Programming
I want to create a program that creates 2 child process, and each of them creates 2 threads, and each thread prints its thread id. I0ve allread done that the outuput isn't the outuput i want.
When a run the following comand "$./a.out | sort -u | wc -l" I have the folowing output
2
$:
It should... (3 Replies)
Discussion started by: pharaoh
3 Replies
LEARN ABOUT LINUX
pthread_self
PTHREAD_SELF(3) Linux Programmer's Manual PTHREAD_SELF(3)
NAME
pthread_self - obtain ID of the calling thread
SYNOPSIS
#include <pthread.h>
pthread_t pthread_self(void);
Compile and link with -pthread.
DESCRIPTION
The pthread_self() function returns the ID of the calling thread. This is the same value that is returned in *thread in the pthread_cre-
ate(3) call that created this thread.
RETURN VALUE
This function always succeeds, returning the calling thread's ID.
ERRORS
This function always succeeds.
CONFORMING TO
POSIX.1-2001.
NOTES
POSIX.1 allows an implementation wide freedom in choosing the type used to represent a thread ID; for example, representation using either
an arithmetic type or a structure is permitted. Therefore, variables of type pthread_t can't portably be compared using the C equality
operator (==); use pthread_equal(3) instead.
Thread identifiers should be considered opaque: any attempt to use a thread ID other than in pthreads calls is nonportable and can lead to
unspecified results.
Thread IDs are only guaranteed to be unique within a process. A thread ID may be reused after a terminated thread has been joined, or a
detached thread has terminated.
The thread ID returned by pthread_self() is not the same thing as the kernel thread ID returned by a call to gettid(2).
SEE ALSO
pthread_create(3), pthread_equal(3), pthreads(7)
COLOPHON
This page is part of release 3.27 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-10-24 PTHREAD_SELF(3)