How Can I use pthread_create ? Post: 95673

9 More Discussions You Might Find Interesting

1. Programming

pthread_create problem

Here is simple code for multithreading in POSIX: void* simplethread(void* arg) { printf("Hello World\n"); } int main(void) { pthread_t id; pthread_create(&id, NULL, simplethread, NULL); return 0; } Whether the new thread will run or not depends on the OS. Tricky ...

2. Programming

unresolve pthread_create etc

how to do with that? after cc -o xxxx xxxx.c ld: Unresolved: _pthread_create _pthread_deteach _pthread_exit Thanks

3. Programming

Pthread_create issue

Hello My problem goes like this: I have used Pthread_create, and I have tryed to create 2 proccess but nothing happens! It does not even matter what the function im trying to create do. It is if im trying to activate an empty function. This is my code. Any help will be highly appreciated....

4. Solaris

pthread_create failed upon execution

Im trying to run an application i compiled (iperf) and i get an error telling me that it cant create the pthread. when i ran the ./configuration one of the things it checked was for pthreads which came back ok. Im not really sure where to even start to resolve this. i have been unable to find...

5. Programming

undefined reference to pthread_create

I try to compile a sample c code in fedora eclipse 3.2 as managed makefile using pthread library,it shows some error on pthread functions.Error is of undefined reference to pthread.Anybody guide me to solve this problem. Thanking you

6. Programming

undefined reference to `pthread_create'

Hi guys. H was learning posix threads in C with anjuta IDE. it gives me undefined reference to `pthread_create' I know i should compile it like: gcc -lpthread main.c how should i import this configuration in anjuta so i can compile inside it?

7. Programming

pthread_create

The prototype for pthread_create function is like this:- int pthread_create(pthread_t *thread,pthread_attr_t *attr,void *(*start routine),void *arg); Q.1 .Why the return type of the start_routine must be void*?? Q.2. Why should we pass arg by converting into void * only ?? Thank You

8. UNIX for Dummies Questions & Answers

Pthread_create problem

Hi, I'm trying to do my homework assignment but I am having trouble using the pthread_create fucntion. Here is my code________________ //Alicia Johnson //sum_pid program //creates n number of threads. These threads create a random number //then adds the number to a global array. Then...

9. Programming

fork vs pthread_create

Suppose I have a simple program main() with a global varibale int x=0. int x = 0; main() { print("%d\n",x); } I want to create two threads/process which must access this variable x in sync. Which one will be better threads( pthread_create ) or process( fork )? If I go with fork() then...

LEARN ABOUT NETBSD

mkstr

MKSTR(1)						    BSD General Commands Manual 						  MKSTR(1)

NAME

     mkstr -- create an error message file by massaging C source

SYNOPSIS

     mkstr [-] messagefile prefix file ...

DESCRIPTION

     mkstr creates files containing error messages extracted from C source, and restructures the same C source, to use the created error message
     file.  The intent of mkstr was to reduce the size of large programs and reduce swapping (see BUGS section below).

     mkstr processes each of the specified files, placing a restructured version of the input in a file whose name consists of the specified
     prefix and the original name.  A typical usage of mkstr is

	   mkstr pistrings xx *.c

     This command causes all the error messages from the C source files in the current directory to be placed in the file pistrings and restruc-
     tured copies of the sources to be placed in files whose names are prefixed with xx.

     Options:

     -	     Error messages are placed at the end of the specified message file for recompiling part of a large mkstr ed program.

     mkstr finds error messages in the source by searching for the string `error("' in the input stream.  Each time it occurs, the C string start-
     ing at the '"' is stored in the message file followed by a null character and a new-line character; The new source is restructured with
     lseek(2) pointers into the error message file for retrieval.

	   char efilname = "/usr/lib/pi_strings";
	   int efil = -1;

	   error(a1, a2, a3, a4)
	   {
		   char buf[256];

		   if (efil < 0) {
			   efil = open(efilname, 0);
			   if (efil < 0) {
	   oops:
				   perror(efilname);
				   exit 1 ;
			   }
		   }
		   if (lseek(efil, a1, 0) < 0 || read(efil, buf, 256) <= 0)
			   goto oops;
		   printf(buf, a2, a3, a4);
	   }

SEE ALSO

     xstr(1), lseek(2)

HISTORY

     mkstr appeared in 3.0BSD.

BUGS

     mkstr was intended for the limited architecture of the PDP-11 family.  Very few programs actually use it.	It is not an efficient method, the
     error messages should be stored in the program text.

BSD
								   June 6, 1993 							       BSD