03-28-2009
Can you get core dump and look at the stack?
8 More Discussions You Might Find Interesting
1. AIX
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
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
What is segmentation fault(core dumped) (1 Reply)
Discussion started by: gokult
1 Replies
4. Programming
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
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
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
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
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
CORE(5) File Formats Manual CORE(5)
NAME
core - format of memory image file
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
The UNIX System writes out a memory image of a terminated process when any of various errors occur. See sigvec(2) for the list of reasons;
the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called
`core' and is written in the process's working directory (provided it can be; normal access controls apply).
The core file consists of the u. area, whose size (in 64 byte `clicks') is defined by the USIZE manifest in the <sys/param.h> file. The
u. area starts with a user structure as given in <sys/user.h>. The rest of the u. area consists of the kernel stack for the terminated
process which includes (among other things) the processor registers at the time of the fault; see the system listings for the format of
this area. The remainder of the core file consists first of the data pages and then the stack pages of the process image. The amount of
data space image in the core file is given (in clicks) by the variable u_dsize in the u. area. If the text segment was not write-only and
and shared it is included as the first etext bytes of the data image where etext is taken from the symbol table of the object file which
generated the memory image. The amount of stack image in the core file is given (in clicks) by the variable u_ssize in the u. area.
In general the debugger adb(1) is sufficient to deal with core images.
SEE ALSO
adb(1), sigvec(2), stack(5)
3rd Berkeley Distribution January 26, 1987 CORE(5)