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
crashdc(8) System Manager's Manual crashdc(8)
NAME
crashdc - Diagnostic data collection for a running or crashed system
SYNOPSIS
/usr/bin/crashdc [system-kernel] [core-image]
DESCRIPTION
The crashdc utility examines the core image of the operating system to extract critical diagnostic data. This utility is a shell script
that invokes several tools and commands that extract selected parameters of a running or a crashed system (for example, system configura-
tion, running processes, and panic messages).
The arguments to the crashdc utility are the system kernel and the core image. The default values are /vmunix and /dev/mem, respectively.
If you specify no arguments, the crashdc utility examines the running system.
The system usually invokes the crashdc utility during system startup. If the most recent core dump has been saved by the savecore command,
both the core image and the system kernel (respectively vmcore.n and vmunix.n, where the variable n is the crash number) are saved in the
crash directory (by default, /var/adm/crash). Also, the crashdc utility saves the output as the file crash-data.n (where the variable n is
the crash number) in the crash directory. The crashdc utility is invoked only if crash-data.n output in the crash directory does not exist
or is not from the most recent crash.
FILES
Default core image Default system image Output from crashdc
SEE ALSO
Commands: dbx(1), kdbx(8), savecore(8)
crashdc(8)
