10 More Discussions You Might Find Interesting
1. Programming
I have discovered a large number of core dumps on one of our OSX machines (dumped into a generic /cores dir).
Is there any way to find out which binary generated them?
Thanks! (2 Replies)
Discussion started by: mirni
2 Replies
2. UNIX for Dummies Questions & Answers
Help!
I have an AIX system that has a power outage.
When I logged in as root and got the system up and running it all looked ok.
But.....when a user tries to log in they receive the error: The perform stack has overflowed OP=2117 PC=2124 E=46 in emmcshflif
icrun is finished
How can I fix... (1 Reply)
Discussion started by: dlegnar
1 Replies
3. Ubuntu
I have built kernel 2.6.35 on my Ubuntu system with some specific requirement. I also built some app defined module with the same kernel. I booted up the built version and I find it did not work properly as there is some gui and other modules missing problem. But the system booted up and I did... (0 Replies)
Discussion started by: sunilsukumar4u
0 Replies
4. Filesystems, Disks and Memory
hello,
when i make gcc 4.4.2 i get this message
find gnu java javax org sun -name .svn -prune -o -name '*.class' -print | \
gjar -cfM@ $here/libgcj-4.4.2.jar
/bin/sh: line 2: 32730 Done find gnu java javax org sun -name .svn -prune -o -name '*.class'... (2 Replies)
Discussion started by: aleppos
2 Replies
5. Red Hat
Hi All,
I am getting "Segmentation fault (core dumped)" error in the runtime. I am new this please can you tell me why is that i am getting this error and I am not sure of my compilation :
gcc -c avc_test.c
gcc -c md5.c
gcc avc_test.o md5.o -shared -Llibcoreavc_sdk.so -o proj
... (1 Reply)
Discussion started by: fido.genial
1 Replies
6. HP-UX
Hi,
I get a problem with stack overflow on HP-UX, when running a C program.
Pid 28737 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
The possible cause i found, was that the definition of a structure had... (0 Replies)
Discussion started by: karthikb23
0 Replies
7. UNIX for Advanced & Expert Users
I use SCO UNIX 5.07 on a Compaq Proliant Machine. Each time I press the Escape or Delete key while running a program or issuing a FoxBase+ command from the dot prompt, I receive the error message: "Memory Fault - Core Dumped" and the screen locks up immediately.
I would appreciate if necessary... (0 Replies)
Discussion started by: bayuz
0 Replies
8. UNIX for Advanced & Expert Users
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
9. Filesystems, Disks and Memory
HI All,
I am working on Solaris 8, i have this application runing on one of the partitions,(the installation was done here ie /export/home)
And the out put of this goes to another parition of other disk attached to the same machine. After a certain period of time is get this error stating... (2 Replies)
Discussion started by: zing
2 Replies
10. UNIX for Dummies Questions & Answers
what is segmentation core dumped?
how should i respond? (9 Replies)
Discussion started by: yls177
9 Replies
gcore(1) BSD General Commands Manual gcore(1)
NAME
gcore -- get core images of running processes
SYNOPSIS
gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid
DESCRIPTION
The gcore program creates a core file image of the process specified by pid. The resulting core file can be used with a debugger, e.g.
lldb(1), to examine the state of the process.
The following options are available:
-s Suspend the process while the core file is captured.
-v Report progress on the dump as it proceeds.
-b size Limit the size of the core file to size MiBytes.
The following options control the name of the core file:
-o path
Write the core file to path.
-c pathformat
Write the core file to pathformat. The pathformat string is treated as a pathname that may contain various special characters which
cause the interpolation of strings representing specific attributes of the process into the name.
Each special character is introduced by the % character. The format characters and their meanings are:
N The name of the program being dumped, as reported by ps(1).
U The uid of the process being dumped, converted to a string.
P The pid of the process being dumped, converted to a string.
T The time when the core file was taken, converted to ISO 8601 format.
% Output a percent character.
The default file name used by gcore is %N-%P-%T. By default, the core file will be written to a directory whose name is determined from the
kern.corefile MIB. This can be printed or modified using sysctl(8).
The directory where the core file is to be written must be accessible to the owner of the target process.
gcore will not overwrite an existing file, nor will it create missing directories in the path.
EXIT_STATUS
The gcore utility exits 0 on success, and >0 if an error occurs.
FILES
/cores/%N-%P-%T default pathname for the corefile.
BUGS
With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image. Such
a partial core dump may confuse subsequent programs that attempt to parse the contents of such files.
SEE ALSO
lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8).
Darwin May 31, 2019 Darwin