Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sigreturn(2) [redhat man page]

SIGRETURN(2)						     Linux Programmer's Manual						      SIGRETURN(2)

NAME
sigreturn - return from signal handler and cleanup stack frame SYNOPSIS
int sigreturn(unsigned long __unused); DESCRIPTION
When the Linux kernel creates the stack frame for a signal handler, a call to sigreturn is inserted into the stack frame so that the the signal handler will call sigreturn upon return. This inserted call to sigreturn cleans up the stack so that the process can restart from where it was interrupted by the signal. RETURN VALUE
sigreturn never returns. WARNING
The sigreturn call is used by the kernel to implement signal handlers. It should never be called directly. Better yet, the specific use of the __unused argument varies depending on the architecture. CONFORMING TO
sigreturn is specific to Linux and should not be used in programs intended to be portable. FILES
/usr/src/linux/arch/i386/kernel/signal.c /usr/src/linux/arch/alpha/kernel/entry.S SEE ALSO
kill(2), signal(2), signal(7) Linux 1.3.20 1995-08-21 SIGRETURN(2)

Check Out this Related Man Page

SIGRETURN(2)						     Linux Programmer's Manual						      SIGRETURN(2)

NAME
sigreturn - return from signal handler and cleanup stack frame SYNOPSIS
int sigreturn(unsigned long __unused); DESCRIPTION
When the Linux kernel creates the stack frame for a signal handler, a call to sigreturn() is inserted into the stack frame so that upon return from the signal handler, sigreturn() will be called. This sigreturn() call undoes everything that was done--changing the process's signal mask, switching stacks (see sigaltstack(2))--in order to invoke the signal handler: it restores the process's signal mask, switches stacks, and restores the process's context (registers, pro- cessor flags), so that the process directly resumes execution at the point where it was interrupted by the signal. RETURN VALUE
sigreturn() never returns. FILES
/usr/src/linux/arch/i386/kernel/signal.c /usr/src/linux/arch/alpha/kernel/entry.S CONFORMING TO
sigreturn() is specific to Linux and should not be used in programs intended to be portable. NOTES
The sigreturn() call is used by the kernel to implement signal handlers. It should never be called directly. Better yet, the specific use of the __unused argument varies depending on the architecture. SEE ALSO
kill(2), sigaltstack(2), signal(2), signal(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-06-26 SIGRETURN(2)
Man Page

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

help required - stack trace

Hi all, One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into... (9 Replies)
Discussion started by: ranj@chn
9 Replies

2. BSD

Installing FreeBSD in VirtualBox

Keeps saying no bootable media found. Works with every other distro. Any ideas? (6 Replies)
Discussion started by: Swathe
6 Replies

3. HP-UX

Core Dump while running Installer

I am running a jvm dependent installer and it crashes midway between the installation. It throws a Core Dump: Stack_Trace: error while unwinding stack ( 0) 0xc4007e2c report_and_die__7VMErrorFv + 0x154 ( 1) 0xc3ee2628 JVM_handle_hpux_signal__Q2_2os4HpuxSFiP9__siginfoPvT1 + 0xaf8 (... (0 Replies)
Discussion started by: rkisho
0 Replies

4. Red Hat

SSH problem

Hey, I have a Red Hat 5.2 machine with : 2.6.18-92.el5 kernel PRM's: openssh-4.3p2-29.el5 openssh-clients-4.3p2-29.el5 openssl-0.9.8e-7.el5 openssh-server-4.3p2-29.el5 openssl-0.9.8b-10.el5 openssl-devel-0.9.8e-7.el5 openssh-askpass-4.3p2-29.el5 I'm trying to transfer files to a... (2 Replies)
Discussion started by: eliraza6
2 Replies

5. Red Hat

RHEL: Users unable to login via SSH

removing the post (6 Replies)
Discussion started by: titanic4u
6 Replies

6. Linux

Sendmail takes too long to start and the host is unable to send emails

Hello All, Sendmail takes too long to start and the host is unable to send emails, below are the steps followed, Please let me know if I'm missing anything, is there a debug mode for mailx? # time service sendmail restart Shutting down sm-client: Shutting... (6 Replies)
Discussion started by: lovesaikrishna
6 Replies

7. Shell Programming and Scripting

ksh file handling

Specifically on RHEL 5.7. When does the underlying ksh process open and close files? Every time they're accessed, or as little as possible? Say you have some script like: CreateFiles() { grep "<VALUE1>" ${infile} >> ${outfile} grep "<VALUE2>" ${infile} >> ${outfile} ...... (4 Replies)
Discussion started by: CarloM
4 Replies

8. UNIX for Advanced & Expert Users

unable to understand the output of TRUSS command

Hi, I am trying to set ulimit for soft stack unlimited, but this is not taking effect, after tracing the ulimit -a unlimited command, the below output was generated, which i am unable to comprehend. Could any one help me with this? prcbap1-r10prod: truss -d ulimit -s unlimited Tue Dec 30... (2 Replies)
Discussion started by: NasirAbbasi
2 Replies

9. SuSE

Sssd not starting- failed

Hi, I am unable to start sssd as its getting failed with below error. OS: SLES 11 Version: 3 # uname -r 2.6.32.59-0.7-default # sssd -d4 ldb: unable to dlopen /usr/lib64/ldb/tdb.so : /usr/lib64/ldb/tdb.so: undefined symbol: tdb_transaction_prepare_commit # /etc/init.d/sssd restart... (14 Replies)
Discussion started by: Sridaran
14 Replies

10. UNIX and Linux Applications

Issue launching Websphere Customization ToolBox

I'm trying to configure IBM customization Tool Box but i'm facing the following issue don't know where i'm going wrong. CentOS Linux release 7.2.1511 (Core) 3.10.0-327.18.2.el7.x86_64 run-level 3 xming is working Unhandled exception Type=Segmentation error vmState=0xd4c6046e... (0 Replies)
Discussion started by: James0806
0 Replies