Sponsored Content
Top Forums Programming C++ Segmentation Fault on exit of main Post 302301759 by pshaikh on Saturday 28th of March 2009 03:18:12 AM
Old 03-28-2009
Can you get core dump and look at the stack?
 

8 More Discussions You Might Find Interesting

1. AIX

Segmentation fault

I am tring to install Lotus Domino/Notes 5.0.5 on a AIX 4.3.3 server. I go to run the cdrom/ibmpow/install and I get the following error. Lotus Notes for Unix Install Program --------------------------------------------- ./install: 10088 Segmentation fault This had Lotus Notes installed... (1 Reply)
Discussion started by: jshaulis
1 Replies

2. Programming

segmentation fault

Hi, I am having this segmentation fault not in the following program, bt. in my lab program . My lab program is horrible long so cannot post it here bt. I am using the following logic in my program which is giving the segmentation fault. Bt. if I run this sample program as it is it dosen't give... (3 Replies)
Discussion started by: mind@work
3 Replies

3. Programming

segmentation fault

What is segmentation fault(core dumped) (1 Reply)
Discussion started by: gokult
1 Replies

4. Programming

Segmentation fault.

I'm getting a segmentation fault. I'm new to Linux programming. Thanks so much for all of your input.:eek: #include </usr/include/mysql++/mysql++.h> #include <stdio.h> #include <iostream> #include <sstream> #include <string.h> using namespace std; int outputToImport(const char*... (1 Reply)
Discussion started by: sepoto
1 Replies

5. Programming

segmentation fault.

This code is causing a segmentation fault and I can't figure out why. I'm new to UNIX and I need to learn how to avoid this segmentation fault thing. Thank you so much. Thanks also for the great answers to my last post.:):b: int main() { mysqlpp::Connection conn(false); if... (3 Replies)
Discussion started by: sepoto
3 Replies

6. Programming

Segmentation fault in C

i have this code int already_there(char *client_names, char *username) { int i; for(i = 0; i<NUM; i++) { printf("HERE\n"); if (strcmp(client_names, username)==0) return(1); } return(0); } and i get a segmentation fault, whats wrong here? (7 Replies)
Discussion started by: omega666
7 Replies

7. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

8. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1... I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one. Below are two very condensed snippets of which I have added the results inside the each code section. IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
SAVECORE(8)						      System Manager's Manual						       SAVECORE(8)

NAME
savecore - save a core dump of the operating system SYNOPSIS
savecore dirname [ system ] DESCRIPTION
Savecore is meant to be called at the end of the /etc/rc file. Its function is to save the core dump of the system (if one was made) and to write a reboot message in the shutdown log. It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n. The second argument is the namelist for the system which made the core image; the current system is always assumed to be /unix. The trailing ".n" in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before savecore writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the file sys- tem which contains dirname than the number obtained from the minfree file, the core dump is not done. If the minfree file does not exist, savecore always writes out the core file (assuming that a core dump was taken). Savecore also writes a reboot message in the shut down log. If the system crashed as a result of a panic, savecore records the panic string in the shut down log too. If savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot. It announces the time that it set when this occurs. FILES
/usr/adm/shutdownlogshutdown log /unix current UNIX BUGS
The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant. This information should be passed to init by the system; however, this is difficult because the system may have to be rebooted a second time if the root filesystem is patched. 3rd Berkeley Distribution SAVECORE(8)
All times are GMT -4. The time now is 07:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy