07-01-2014
My reading of the core man page suggests that by default a "file-backed shared mapping" will not be dumped.
Quote:
The default value of coredump_filter is 0x3; this reflects traditional Linux behavior and means that only anonymous memory segments are dumped.
So if he has a recent kernel he can override this and get the region dumped. But that option will not exist on older kernels.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine.
Q is how does one read this core file, or I should say 'what is this core file'?
thnx (2 Replies)
Discussion started by: buRst
2 Replies
4. UNIX for Advanced & Expert Users
I am running HP-UX B.11.11.
I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used.
But when I try to start the DB with the increased buffer parameter I get told.
"Not... (1 Reply)
Discussion started by: cjcamaro
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
6. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
7. HP-UX
i am getting memory fault (core dump) in a C program
i want to know which statement execution caused it.
i tried following things
$ gdb generalised_tapinread_mod
HP gdb 5.4.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.... (2 Replies)
Discussion started by: junaid.nehvi
2 Replies
8. UNIX for Advanced & Expert Users
Hi Guys,
I work on a AIX environment and I'm trying to write a script where I can collect all the memory used by a process. Basically I'm executing the command 'ps -fu userid' to get all the process ids and then executing the 'ps v PID' to get all the memory allocated by PPID. My question is... (2 Replies)
Discussion started by: arizah
2 Replies
9. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
10. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 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