Above all, why use boost?
1) It's simply a learning trial by "copy-paste" and still at stage of "try and error" to understand more, hopefully;
2) The purpose is to make a function which will be combined to other .cpp code. Modified from a snippet online as was told "ultra-fast"!
Am I stubborn and offending if I insist C++, as I need modify your code to reverse the output and then integrate it into other .cpp code?
Thanks a lot in any way!
When run it, segment fault.
What is wrong?
#include <stdio.h>
#include <stdlib.h>
const int max =20;
//****************************************************
// Input Matrix
//****************************************************
void inMatrixAA(int *AA, int row, int col)... (9 Replies)
Dear all,
I used debugger from C++ and these are the message I got:
Program received signal SIGSEGV, Segmentation fault.
0x00323fc0 in free () from /lib/tls/libc.so.6
(gdb) info s
#0 0x00323fc0 in free () from /lib/tls/libc.so.6
#1 0x00794fa1 in operator delete () from... (5 Replies)
Hi
some help read............
I'm getting a segmentation fault when I run an AIX COBOL/Db2 program.
I initiate the program from the command line, but it hangs, and then when I press enter it generates a segmantation fault and produces a core dump.
The box is running AIX software level ... (5 Replies)
Hi all
In the ltp-posix test,there is a case in open_posix_testsuite\conformance\interfaces\timer_gettime\speculative/6-1.c
I run the above code,it will has a segment fault, if I modify it to below,it works well
Anybody can tell me why? (1 Reply)
I´m writing this program in QNX , I`m kinda new to UNIX and programing in general, and when I try to run it it gives me the Memory Fault error. Can anyone help?
#include <stdio.h>
#include <fcntl.h>
void main(void)
{int a,ter;
char buf;
printf("a=");
scanf("%d",a);
ter=open... (6 Replies)
Hi,
Whether the following piece of code is placed in the read-only memory of code (text) segment or data segment?
char *a = "Hello";
I am getting two different answers while searching in google :( that's why the confusion is (7 Replies)
I always get segment fault, why? can sb help me and modify it, I have spend on much time on
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/time.h>
#include <string.h>
#define MAX 10
pthread_t thread;
void *thread1()
{
int *a;
int i, n;
... (1 Reply)
Hello everybody,
I've been working on a program on my Linux box, after finished the code, i compile it with gcc -Wall option, so i can see what's wrong or unused.
The Walll output shows nothing, so there are no loose ends on the program.
I run the program on my system, and it works PERFECTLY.... (5 Replies)
Hi
I have struggling a week to fix a program , in the begining i got SIGBUS , but after many attempts still the program gets SIGSEGV segment fault , In bellow i post the seg fault log + source codes. would really appreciate if experts help me to fix this segment fault error. any advice is... (2 Replies)
Hello,
This function was copied into my code, which was compiled without error/warning, but when executed there is always Segmentation fault at the end after the output (which seems correct!):
void get_hashes(unsigned int hash, unsigned char *in)
{
unsigned char *str = in;
int pos =... (7 Replies)
Discussion started by: yifangt
7 Replies
LEARN ABOUT ULTRIX
pfm_cleanup
pfm_cleanup(3ncs)pfm_cleanup(3ncs)Name
pfm_cleanup - establish a clean-up handler
Syntax
#include <idl/c/base.h>
#include <idl/c/pfm.h>
status_$t pfm_$cleanup(cleanup_record)
pfm_$cleanup_rec *cleanup_record;
Arguments
cleanup_record A record of the context when is called. A program should treat this as an opaque data structure and not try to alter
or copy its contents. It is needed by and to restore the context of the calling process at the clean-up handler entry
point.
Description
The routine establishes a clean-up handler that is executed when a fault occurs. A clean-up handler is a piece of code executed before a
program exits when a signal is received by the process. The clean-up handler begins where is called; the routine registers an entry point
with the system where program execution resumes when a fault occurs. When a fault occurs, execution resumes after the most recent call to
There can be more than one clean-up handler in a program. Multiple clean-up handlers are executed consecutively on a last-in/first-out
basis, starting with the most recently established handler and ending with the first clean-up handler. The system provides a default
clean-up handler established at program invocation. The default clean-up handler is always called last, just before a program exits, and
releases any system resources still held, before returning control to the process that invoked the program.
Diagnostics
When called to establish a clean-up handler, returns the status pfm_$cleanup_set to indicate the clean-up handler was successfully estab-
lished. When the clean-up handler is entered in response to a fault signal, effectively returns the value of the fault that triggered the
handler.
This section lists status codes for errors returned by this routine in
pfm_$bad_rls_order Attempted to release a clean-up handler out of order.
pfm_$cleanup_not_found
There is no pending clean-up handler.
pfm_$cleanup_set A clean-up handler was established successfully.
pfm_$cleanup_set_signaledl
Attempted to use pfm_$cleanup_set as a signal.
pfm_$invalid_cleanup_rec
Passed an invalid clean-up record to a routine.
pfm_$no_space Cannot allocate storage for a clean-up handler. Clean-up handler code runs with asynchronous faults inhibited. When
returns something other than pfm_$cleanup_set indicating that a fault has occurred, there are four possible ways to
leave the clean-up code:
o The program can call to start the next clean-up handler with a different fault signal.
o The program can call to start the next clean-up handler with the same fault signal.
o The program can continue with the code following the clean-up handler. It should generally call to reenable
asynchronous faults. Execution continues from the end of the clean-up handler code; it does not resume where
the fault signal was received.
o The program can reestablish the handler by calling before proceeding.
FilesSee Alsointro(3ncs), pfm_signal(3ncs)pfm_cleanup(3ncs)