Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

abort(3) [osf1 man page]

abort(3)						     Library Functions Manual							  abort(3)

NAME
abort - Generates a software signal to end the current process LIBRARY
Standard C Library (libc.so, libc.a) SYNOPSIS
#include <stdlib.h> void abort ( void ); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: abort(): ISO C, POSIX.1, XPG4, XPG4-UNIX Refer to the standards(5) reference page for more information about industry standards and associated tags. DESCRIPTION
The abort() function sends a SIGABRT signal to the current process. This signal terminates the process unless both of the following condi- tions are true: (1) signal SIGABRT is being caught, and (2) the signal handler does not do a normal return, for example, if it does a longjmp. If abort() causes the process to terminate abnormally and the current directory is writable, the system creates a core file in the current working directory. If the call to the abort() function terminates the process, each open stream and message catalog descriptor is affected as if the fclose() function was called. The abort() function then terminates the process with the same result as the _exit() function, with the exception of the status value made available to the wait() or waitpid() function. These functions receive the status value of the process terminated by the SIGABRT signal. The abort() function overrides blocking or ignoring of the SIGABRT signal. NOTES
The abort() function is supported for multi-threaded applications. RELATED INFORMATION
Functions: exit(2), kill(2), sigaction(2) Standards: standards(5) delim off abort(3)

Check Out this Related Man Page

ABORT(3)						     Linux Programmer's Manual							  ABORT(3)

NAME
abort - cause abnormal process termination SYNOPSIS
#include <stdlib.h> void abort(void); DESCRIPTION
The abort() first unblocks the SIGABRT signal, and then raises that signal for the calling process. This results in the abnormal termina- tion of the process unless the SIGABRT signal is caught and the signal handler does not return (see longjmp(3)). If the abort() function causes process termination, all open streams are closed and flushed. If the SIGABRT signal is ignored, or caught by a handler that returns, the abort() function will still terminate the process. It does this by restoring the default disposition for SIGABRT and then raising the signal for a second time. RETURN VALUE
The abort() function never returns. CONFORMING TO
SVr4, POSIX.1-2001, 4.3BSD, C89, C99. SEE ALSO
gdb(1), sigaction(2), exit(3), longjmp(3), 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/. GNU
2007-12-15 ABORT(3)
Man Page

5 More Discussions You Might Find Interesting

1. Programming

Program received signal SIGABRT, Aborted.

I ran degugger in C++ and the followings are the message I got: Program received signal SIGABRT, Aborted. 0x002a57a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) info s #0 0x002a57a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x002e97f5 in raise () from /lib/tls/libc.so.6... (1 Reply)
Discussion started by: napapanbkk
1 Replies

2. UNIX for Advanced & Expert Users

examine core file after abort()

I'm running Red Hat Linux 2.6.7 on a x86_64 box. I have a core file from a program that called abort(). Does anyone here know how can I get a backtrace? (Re-creating the error with svd running inside gdb has proved impossible). % gdb svd core.25223 GNU gdb Red Hat Linux... (2 Replies)
Discussion started by: svact
2 Replies

3. Shell Programming and Scripting

Problem in checking file abort

Hi, I would like to know given executing a file with inputs, I would like to know when does it terminate /abort abnormally. I tried to append an echo $? after executing my program which is in C. However, there is nothing..It shows 0 even though the program actually exit. my command is... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

4. UNIX for Advanced & Expert Users

Ignored signals & blocking system calls

If I explicity ignore a signal (for example, SIGALRM), and this signal is generated during a blocking system call (for example, a recvfrom() ), what happens to the system call? Does it abort, or does it remain blocked until its end? (2 Replies)
Discussion started by: hurricane
2 Replies

5. Programming

Why do I receive Program received signal SIGABRT, Aborted?

Im using gdb and when a user disconnects from my server I receive a message Program received signal SIGABRT, Aborted. 0x7ffe0304 in ?? () I was hoping someone here might have a explination for this message in gdb (26 Replies)
Discussion started by: Errigour
26 Replies