10 More Discussions You Might Find Interesting
1. Red Hat
I would like to understand how many number of CPUs and cores do I have on my server based on following out put..
Few observations... Please correct me if I am wrong
Since Physical ID is same CPU is singe
It has 8 virtual processors
Hyper thrading is enabled since no of siblings are... (1 Reply)
Discussion started by: parth_buch
1 Replies
2. 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
3. Red Hat
How to now if the server is core dumping into the same filesystem? (4 Replies)
Discussion started by: 300zxmuro
4 Replies
4. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
5. Red Hat
I want to use linux which core version is 2.4.0,so I want to know which version redhat linux contains core 2.4.0? Where can I get this version redlinux?
Thanks (2 Replies)
Discussion started by: konvalo
2 Replies
6. Programming
I have a dual core pc, I write a application with two child process.
I know I can add sched_get_cpu to know the process run on which core, but, it just when the sched_get_cpu is called, it will tell me the result, my quesion is how to know the child proceess spend how many times on one core. (2 Replies)
Discussion started by: yanglei_fage
2 Replies
7. UNIX for Dummies Questions & Answers
Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies
8. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
9. Linux
I've been using FC2, but my sound card doesn't work
I'm new with linux systems..
but there says that needs to recompile kernel
how can i do it with a kernel 2.6.5 i386 ?
by the way,. my sound card chipset is an ESS 1869F, with a compaq deskpro Smal Form Factor. but i have not found a... (4 Replies)
Discussion started by: Quake
4 Replies
10. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 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
