Sponsored Content
Top Forums Programming Parent Thread Of Child Thread Post 302486013 by Loic Domaigne on Thursday 6th of January 2011 05:23:12 PM
Old 01-06-2011
Good Evening,

Quote:
Originally Posted by rupeshkp728
Parent Thread Of Child Thread
We are not able to get the parent thread id of this thread?
Will anybody let us know how to find the parent of such randomly created threads?
Let's go to the core question as it's near bed time Smilie

From a pure POSIX standpoint, if we want to get the "parent thread id" (the term "parent thread" is BTW is misnomer since POSIX states that all threads are peers), you need to keep track of the "thread's tree" yourself.

Now specifically, if you tell us which OS is (are) targeted, we may perhaps find an OS specific solution.

Cheers, Loïc
This User Gave Thanks to Loic Domaigne For This Post:
 

5 More Discussions You Might Find Interesting

1. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies

2. Programming

How can I make the parent thread wait

Hi All, I will be glad if you could help me resolve this problem. I have created two detachable threads and wanted to them execute independent of the parent thread ( the main task which creates the detachable threads). But I see no output coming from the execution of two detachable threads.... (4 Replies)
Discussion started by: jayfriend
4 Replies

3. Shell Programming and Scripting

forking a child process and kill its parent to show that child process has init() as its parent

Hi everyone i am very new to linux , working on bash shell. I am trying to solve the given problem 1. Create a process and then create children using fork 2. Check the Status of the application for successful running. 3. Kill all the process(threads) except parent and first child... (2 Replies)
Discussion started by: vizz_k
2 Replies

4. Programming

Killing a Child Thread

What is the best way for a parent to kill a child thread that has blocked on a command it cannot finish and will never read another line of its code? Will pthread_cancel() work with a thread that will never stop processing its current line of code? Thanks. (4 Replies)
Discussion started by: Brandon9000
4 Replies

5. Programming

Child threads communicating with main thread via pipes

I have a simple client/server program I am using for learning purposes. I have it setup so that after server is setup and listening it than goes into a loop where it accepts incoming client connections. After each connection, the client socket is than passed to a thread routine where it can be... (3 Replies)
Discussion started by: Majortom71
3 Replies
Thread::Semaphore(3pm)					 Perl Programmers Reference Guide				    Thread::Semaphore(3pm)

NAME
Thread::Semaphore - Thread-safe semaphores VERSION
This document describes Thread::Semaphore version 2.12 SYNOPSIS
use Thread::Semaphore; my $s = Thread::Semaphore->new(); $s->down(); # Also known as the semaphore P operation. # The guarded section is here $s->up(); # Also known as the semaphore V operation. # Decrement the semaphore only if it would immediately succeed. if ($s->down_nb()) { # The guarded section is here $s->up(); } # Forcefully decrement the semaphore even if its count goes below 0. $s->down_force(); # The default value for semaphore operations is 1 my $s = Thread::Semaphore->new($initial_value); $s->down($down_value); $s->up($up_value); if ($s->down_nb($down_value)) { ... $s->up($up_value); } $s->down_force($down_value); DESCRIPTION
Semaphores provide a mechanism to regulate access to resources. Unlike locks, semaphores aren't tied to particular scalars, and so may be used to control access to anything you care to use them for. Semaphores don't limit their values to zero and one, so they can be used to control access to some resource that there may be more than one of (e.g., filehandles). Increment and decrement amounts aren't fixed at one either, so threads can reserve or return multiple resources at once. METHODS
->new() ->new(NUMBER) "new" creates a new semaphore, and initializes its count to the specified number (which must be an integer). If no number is specified, the semaphore's count defaults to 1. ->down() ->down(NUMBER) The "down" method decreases the semaphore's count by the specified number (which must be an integer >= 1), or by one if no number is specified. If the semaphore's count would drop below zero, this method will block until such time as the semaphore's count is greater than or equal to the amount you're "down"ing the semaphore's count by. This is the semaphore "P operation" (the name derives from the Dutch word "pak", which means "capture" -- the semaphore operations were named by the late Dijkstra, who was Dutch). ->down_nb() ->down_nb(NUMBER) The "down_nb" method attempts to decrease the semaphore's count by the specified number (which must be an integer >= 1), or by one if no number is specified. If the semaphore's count would drop below zero, this method will return false, and the semaphore's count remains unchanged. Otherwise, the semaphore's count is decremented and this method returns true. ->down_force() ->down_force(NUMBER) The "down_force" method decreases the semaphore's count by the specified number (which must be an integer >= 1), or by one if no number is specified. This method does not block, and may cause the semaphore's count to drop below zero. ->up() ->up(NUMBER) The "up" method increases the semaphore's count by the number specified (which must be an integer >= 1), or by one if no number is specified. This will unblock any thread that is blocked trying to "down" the semaphore if the "up" raises the semaphore's count above the amount that the "down" is trying to decrement it by. For example, if three threads are blocked trying to "down" a semaphore by one, and another thread "up"s the semaphore by two, then two of the blocked threads (which two is indeterminate) will become unblocked. This is the semaphore "V operation" (the name derives from the Dutch word "vrij", which means "release"). NOTES
Semaphores created by Thread::Semaphore can be used in both threaded and non-threaded applications. This allows you to write modules and packages that potentially make use of semaphores, and that will function in either environment. SEE ALSO
Thread::Semaphore Discussion Forum on CPAN: <http://www.cpanforum.com/dist/Thread-Semaphore> threads, threads::shared MAINTAINER
Jerry D. Hedden, <jdhedden AT cpan DOT org> LICENSE
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.18.2 2013-11-04 Thread::Semaphore(3pm)
All times are GMT -4. The time now is 02:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy