threaded program turns into "forked"

threaded program turns into "forked"

[Alvarez Alberto-AALVARB1]

Hi all,
	a work mate has a program which creates up to 5 threads:

	( this is done at the "main" module)
		 for (i=0;i<numeroSM;i++)
		  {
		     rc=thr_create(NULL,NULL,RecogerCDRs,(void *)i,NULL,&hilo);
		  }

		but, "sometimes" (horrible expression) a child turns up: new process (new pid), whose parent id and command is the former process.
		 AFAIK, thread creation can't "fork" a program.

		The only data i know is that the second process starts 1 second after the first, which could easily occur while thread creation. 
		Just in case it's important, we're working with a socket per thread.

		Does anyone know whether thread creation could be the reason?

		TIA

Alberto Álvarez Besada

Tlf.:        +34 914002155
e-mail.:   aalvarb1@motorola.com
            

-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: threaded program turns into "forked"

[Chuck Winters]

On Thu, Mar 13, 2003 at 05:14:45PM +0100, Alvarez Alberto-AALVARB1 wrote:
> Hi all,
> 	a work mate has a program which creates up to 5 threads:
> 
> 	( this is done at the "main" module)
> 		 for (i=0;i<numeroSM;i++)
> 		  {
> 		     rc=thr_create(NULL,NULL,RecogerCDRs,(void *)i,NULL,&hilo);
> 		  }
> 
> 		but, "sometimes" (horrible expression) a child turns up: new process (new pid), whose parent id and command is the former process.
> 		 AFAIK, thread creation can't "fork" a program.
> 
> 		The only data i know is that the second process starts 1 second after the first, which could easily occur while thread creation. 
> 		Just in case it's important, we're working with a socket per thread.
> 
> 		Does anyone know whether thread creation could be the reason?
> 
> 		TIA
> 
> Alberto ?lvarez Besada
> 
> Tlf.:        +34 914002155
> e-mail.:   aalvarb1@motorola.com
>             
> 

If you are stating that a new child process turns up when a thread is created,
then what you are explaining is the correct behavior.  I believe(someone correct
me if I am wrong), that the pthreads package uses the clone(2) system call which
basically creates a new process with some shared resources.  So, each new thread
will have a different process id with the parent being the process which spawned
the thread.

Chuck