06-30-2011
Thanks for your explanation Corona.
I would like add few things about the context where the code is found. This acutaly found inside the marco current, which will hold the process descriptor being accessed by the process running on a particular CPU.
the process desccriptor pointer is stored in one end of the kernel stack which usually of 8192 bytes.
4 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am trying to compile our linux code base in solaris and came across the following issues. Am I suppose to do something special ?
Can anyone help me to fix this issue.
System :
uname -a
SunOS aspen 5.10 Generic_125100-08 sun4u sparc SUNW,Sun-Fire-280R
The complier that I am using is... (0 Replies)
Discussion started by: learningkid
0 Replies
2. Shell Programming and Scripting
Dear friends,
please tell me how to find the files which are existing in the current directory, but it sholud not search in the sub directories..
it is like this,
current directory contains
file1, file2, file3, dir1, dir2
and dir1 conatins
file4, file5
and dir2 contains
file6,... (9 Replies)
Discussion started by: swamymns
9 Replies
3. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
4. Shell Programming and Scripting
If I enter (simplified):
find . -printf "%p\n"
then all files in the output are prepended by a "." like
./local/share/test23.log
How can achieve that
a.) the leading "./" is omitted
and/or
b.) the full path to the current directory is inserted (enclosed by brackets and a blank)... (1 Reply)
Discussion started by: pstein
1 Replies
LEARN ABOUT ULTRIX
sigstack
sigstack(2) System Calls Manual sigstack(2)
Name
sigstack - set or get signal stack context
Syntax
#include <signal.h>
struct sigstack {
caddr_t ss_sp;
int ss_onstack;
};
sigstack(ss, oss)
struct sigstack *ss, *oss;
Description
The system call allows users to define an alternate stack on which signals are to be processed. If ss is nonzero, it specifies a signal
stack on which to deliver signals and tells the system if the process is currently executing on that stack. When a signal's action indi-
cates its handler should execute on the signal stack (specified with a call), the system checks to see if the process is currently execut-
ing on that stack. If the process is not currently executing on the signal stack, the system arranges a switch to the signal stack for the
duration of the signal handler's execution. If oss is nonzero, the current signal stack state is returned.
Signal stacks are not grown'automatically, as is done for the normal stack. If the stack overflows, unpredictable results may occur.
Return Values
Upon successful completion, a value of zero (0) is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
Diagnostics
The system call fails and the signal stack context remains unchanged, if one of the following occurs.
[EFAULT] Either ss or oss points to memory that is not a valid part of the process address space.
See Also
sigvec(2), setjmp(3)
sigstack(2)