Sponsored Content
Full Discussion: Infinite thread
Top Forums Programming Infinite thread Post 302482971 by Praveen_218 on Thursday 23rd of December 2010 07:54:49 AM
Old 12-23-2010
Quote:
Originally Posted by Loic Domaigne
Good evening,

This is slightly incorrect. A uncaught signal won't necessarily cause main() to go away. What happens actually, is that the signal is delivered to a particular thread in the process.

HTH, Loïc
Which thread it is delivered, if its not main() ? Request you to kindly explain in details.
 

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

high priority thread contains an infinite loop

Hi, Assume there are 3 threads N1, N2, N3. in N1 { .... while(1) { } } when the thread N1 got the time slice, it started executing the infinite loop.. Note:there is no condition inside the while(1) to end the infinite loop I heard that some RTOS will solve this problem... (0 Replies)
Discussion started by: rvan
0 Replies

3. Shell Programming and Scripting

Infinite while loop

what is the difference between while:,while true and while false? (6 Replies)
Discussion started by: proactiveaditya
6 Replies

4. Homework & Coursework Questions

Help with infinite loop problem

1. The problem statement, all variables and given/known data: My problem is an infinite loop when i press any other key other then Y or y in the while loop. what i want it to do is return to the normal script outside of it if pressing N or n or keep asking the same question if its any other... (4 Replies)
Discussion started by: Ren_kun
4 Replies

5. Shell Programming and Scripting

How to stop infinite loop

Im unable to stop the below infinite loop (bash script). Can someone tell me why this isnt responding to signals eg: ctrl+c (SIGINT) or ctrl+z c=0 test_loop() { c=$(($c+1)) echo "count value is : $c " sleep 1 test_loop } Im using: SunOS 5.10 PS: If run this as... (13 Replies)
Discussion started by: Arun_Linux
13 Replies
SIGWAITINFO(2)						     Linux Programmer's Manual						    SIGWAITINFO(2)

NAME
sigwaitinfo, sigtimedwait - synchronously wait for queued signals SYNOPSIS
#include <signal.h> int sigwaitinfo(const sigset_t *set, siginfo_t *info); int sigtimedwait(const sigset_t *set, siginfo_t *info, const struct timespec *timeout); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): sigwaitinfo(), sigtimedwait(): _POSIX_C_SOURCE >= 199309L DESCRIPTION
sigwaitinfo() suspends execution of the calling thread until one of the signals in set is delivered. (If one of the signals in set is already pending for the calling thread, sigwaitinfo() will return immediately with information about that signal.) sigwaitinfo() removes the delivered signal from the set of pending signals and returns the signal number as its function result. If the info argument is not NULL, then it returns a structure of type siginfo_t (see sigaction(2)) containing information about the signal. Signals returned via sigwaitinfo() are delivered in the usual order; see signal(7) for further details. sigtimedwait() operates in exactly the same way as sigwaitinfo() except that it has an additional argument, timeout, which enables an upper bound to be placed on the time for which the thread is suspended. This argument is of the following type: struct timespec { long tv_sec; /* seconds */ long tv_nsec; /* nanoseconds */ } If both fields of this structure are specified as 0, a poll is performed: sigtimedwait() returns immediately, either with information about a signal that was pending for the caller, or with an error if none of the signals in set was pending. RETURN VALUE
On success, both sigwaitinfo() and sigtimedwait() return a signal number (i.e., a value greater than zero). On failure both calls return -1, with errno set to indicate the error. ERRORS
EAGAIN No signal in set was delivered within the timeout period specified to sigtimedwait(). EINTR The wait was interrupted by a signal handler; see signal(7). (This handler was for a signal other than one of those in set.) EINVAL timeout was invalid. CONFORMING TO
POSIX.1-2001. NOTES
In normal usage, the calling program blocks the signals in set via a prior call to sigprocmask(2) (so that the default disposition for these signals does not occur if they are delivered between successive calls to sigwaitinfo() or sigtimedwait()) and does not establish han- dlers for these signals. In a multithreaded program, the signal should be blocked in all threads to prevent the signal being delivered to a thread other than the one calling sigwaitinfo() or sigtimedwait()). The set of signals that is pending for a given thread is the union of the set of signals that is pending specifically for that thread and the set of signals that is pending for the process as a whole (see signal(7)). If multiple threads of a process are blocked waiting for the same signal(s) in sigwaitinfo() or sigtimedwait(), then exactly one of the threads will actually receive the signal if it is delivered to the process as a whole; which of the threads receives the signal is indeter- minate. POSIX leaves the meaning of a NULL value for the timeout argument of sigtimedwait() unspecified, permitting the possibility that this has the same meaning as a call to sigwaitinfo(), and indeed this is what is done on Linux. On Linux, sigwaitinfo() is a library function implemented on top of sigtimedwait(). SEE ALSO
kill(2), sigaction(2), signal(2), signalfd(2), sigpending(2), sigprocmask(2), sigqueue(2), sigsetops(3), sigwait(3), signal(7), time(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-04 SIGWAITINFO(2)
All times are GMT -4. The time now is 07:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy