Sponsored Content
Full Discussion: Signalsafe data structures
Top Forums Programming Signalsafe data structures Post 302579829 by littlegnome on Tuesday 6th of December 2011 06:13:57 PM
Old 12-06-2011
Signalsafe data structures

Hello,

I have a signal handler which manipulates a data structure. The data structure's operations aren't atomic. So if two threads/processes are in a critical section at the same time the data structure will be broken.

With threads you can avoid this stuff with semaphores etc.
However, signal handlers work a bit different than threads. If a signal handler is currently manipulating the data structure and during this the signal handler is called again, then the following happens:

It cannot access the data structure because the first signal handler has it locked, which results in a deadlock.

How can I avoid it but still manipulate my data structure? I cannot lose signals either.
 

3 More Discussions You Might Find Interesting

1. Programming

Recommendations For Generic C Data Structures & Algorithms

Hi All, Rather than re-invent the wheel, I am trying to find a mature C library that provides generic support for lists, trees, etc. I understand C doesn't formally support "generics", but am aware of a few solutions like GLib and SGLib. Can anyone kindly recommend what they think is best?... (1 Reply)
Discussion started by: tristan12
1 Replies

2. Programming

shared memory - userdefined data structures

Hello, I wonder if I can write my userdefined data structures(ex: a list) to a shared memory segment? I know, the shm functions get (void*) parameter so I should be able to read and write a list into the shared memory. may someone inform and clarify me about that, please? (1 Reply)
Discussion started by: xyzt
1 Replies

3. Shell Programming and Scripting

Perl Data Structures

Here is what i need to do. @data #has all column wise data so say info for col 1 location for all rows would be in this array $array = \@data But i need to create a file which should contain these information in a format for all columns even if i have got no values from some of the index... (0 Replies)
Discussion started by: dinjo_jo
0 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 01:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy