Sponsored Content
Full Discussion: Atomicity
Top Forums Programming Atomicity Post 50838 by S.P.Prasad on Tuesday 4th of May 2004 02:19:26 AM
Old 05-04-2004
Thanks Perderabo.

Currently I am going through the algorithms as provided by you in a link.

I would like to put forward my observations in this post. As earlier mentioned the code was ported from VMS to Tru64 to AIX. Now as a part of unit integration, I copied the existing LOCK() and REL() functions in AIX box to that in Tru64 and re-compiled the executables. Surprisingly I did not receive any errors in Tru64. I wonder why ?


And will Shared libraries help us to our problem. We can resist only one copy of functions in the memory and validate which address is getting locked or release and take action accordingly.

Thanks in advance.
 
GSIGNAL(3)						     Linux Programmer's Manual							GSIGNAL(3)

NAME
gsignal, ssignal - software signal facility SYNOPSIS
#include <signal.h> typedef void (*sighandler_t)(int); int gsignal(intsignum); sighandler_t ssignal(int signum, sighandler_t action); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): gsignal(), ssignal(): _SVID_SOURCE DESCRIPTION
Don't use these functions under Linux. Due to a historical mistake, under Linux these functions are aliases for raise(3) and signal(2), respectively. Elsewhere, on System V-like systems, these functions implement software signaling, entirely independent of the classical signal(2) and kill(2) functions. The function ssignal() defines the action to take when the software signal with number signum is raised using the func- tion gsignal(), and returns the previous such action or SIG_DFL. The function gsignal() does the following: if no action (or the action SIG_DFL) was specified for signum, then it does nothing and returns 0. If the action SIG_IGN was specified for signum, then it does noth- ing and returns 1. Otherwise, it resets the action to SIG_DFL and calls the action function with argument signum, and returns the value returned by that function. The range of possible values signum varies (often 1-15 or 1-17). CONFORMING TO
These functions are available under AIX, DG/UX, HP-UX, SCO, Solaris, Tru64. They are called obsolete under most of these systems, and are broken under Linux libc and glibc. Some systems also have gsignal_r() and ssignal_r(). SEE ALSO
kill(2), signal(2), raise(3) COLOPHON
This page is part of release 3.25 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/. 2007-07-26 GSIGNAL(3)
All times are GMT -4. The time now is 02:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy