01-04-2008
yes, v know the binary version, which caused the core dump but dont know in which mode it is built. v r using the same version of the binary to analyse the core, but unable to get the information from the core
Is there any way to analyse the core file ?
this is the o/p of uname -a
HP-UX sh1hp11i B.11.11 U 9000/800 872839660 unlimited-user license
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am facing the following issue when using db2. The JDBC prepared statement command is sending an incorrect value to the database for search. I did a truss on the app and here is the log. I want to know what is the value that is getting passed. is it possible.
26867/68: send(62,... (2 Replies)
Discussion started by: buytamil
2 Replies
2. UNIX for Dummies Questions & Answers
Is it possible to track the progress of a job (informatica) by analysing the progress of it's log file ? I have a long running job, and no way of tracking how far allong it is. Thanks. (4 Replies)
Discussion started by: cosmos328is
4 Replies
3. 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
4. UNIX for Dummies Questions & Answers
I'm not sure if this query is relevant to this forum but here goes anyways...
I want analyse log files that do not appear to be of standard format. I have tried using Analog but cannot config it to read the files.
Does anyone have any advice on working with log files taken from a Unix... (6 Replies)
Discussion started by: Sepia
6 Replies
5. Solaris
Friends
I was trying to analyse a core dump using pstack command in Sol5.9(Sparc)
The output is as below.
root: pstack core_mumux211_istauth_220_108_1229517198_21922
core 'core_mumux211_istauth_220_108_1229517198_21922' of 21922: istauth
fe1afbb8 ttcdrv (c10e0, c1db4, 30ad8, bc950, 0, 0)... (1 Reply)
Discussion started by: efunds
1 Replies
6. Shell Programming and Scripting
Hello,
I have a list of e-mails. I need to know, which email-s from that list not use. I want to do this things:
- take email address from email list
- find this address in mail logs
- if, there is no record about this e-mail adress in list, show this e-mail address on screen
I did... (0 Replies)
Discussion started by: naezdnik
0 Replies
7. Shell Programming and Scripting
Hi,
I have below type of data in a text file in unix.
Emp_Name Emp_Dept
Raj 101
Amruta 100
Shilpa 100
Rohit 123
Amol 198
Rosh 101
Gaurav 198
Number of employees can be even more.
Need a command or a... (2 Replies)
Discussion started by: rajneesh_kapoor
2 Replies
8. Shell Programming and Scripting
Hi,
I need to query Oracle database for 100 users. I have these 100 users in a file. I need a shell script which would read this User file (one user at a time) & query database.
For instance:
USER CITY
--------- ----------
A CITY_A
B CITY_B
C ... (2 Replies)
Discussion started by: DevendraG
2 Replies
9. AIX
Dear Experts,
Am using nmon analyser version 3.3g, and when i tried analyzing my current nmon file it was done successfully. But the problem is all my old nmon files are compressed. So i uncompressed and analyzed using the same analyzer. but got this error
no valid input data! nmon run may... (8 Replies)
Discussion started by: jayadeava
8 Replies
10. Shell Programming and Scripting
Attached is the log file that I have generated through the following script:
last | head -2 |sed '2q;d' |awk '{ print $1"\t"$2"\t"$3"\t\t"$4"\t"$5"\t"$6"\t"$7"\t"$8"\t" $9"\t"$10"\t"$11}'>>/var/log/logadmin/logtest.txt
But now I'm unable to run the following operations on it:
1. Count... (1 Reply)
Discussion started by: Lionking93
1 Replies
CORE(5) BSD File Formats Manual CORE(5)
NAME
core -- memory image file format
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to
disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default
programname.core in the working directory; provided the terminated process had write permission in the directory, and provided the abnormal-
ity did not cause a system crash. (In this event, the decision to save the core file is arbitrary, see savecore(8).)
The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created.
The name of the file is controlled via the sysctl(8) variable kern.corefile. The contents of this variable describes a filename to store the
core image to. This filename can be absolute, or relative (which will resolve to the current working directory of the program generating
it).
The following format specifiers may be used in the kern.corefile sysctl to insert additional information into the resulting core file name:
%H Machine hostname.
%I An index starting at zero until the sysctl debug.ncores is reached. This can be useful for limiting the number of corefiles
generated by a particular process.
%N process name.
%P processes PID.
%U process UID.
The name defaults to %N.core, yielding the traditional FreeBSD behaviour.
By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be
changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1.
Corefiles can be compressed by the kernel if the following items are included in the kernel configuration file:
options COMPRESS_USER_CORES
devices gzio
When COMPRESS_USER_CORES is included the following sysctls can control if core files will be compressed:
kern.compress_user_cores_gzlevel Gzip compression level. Defaults to -1.
kern.compress_user_cores Actually compress user cores. Core files will have the suffix .gz appended to them.
EXAMPLES
In order to store all core images in per-user private areas under /var/coredumps, the following sysctl(8) command can be used:
sysctl kern.corefile=/var/coredumps/%U/%N.core
SEE ALSO
gdb(1), kgdb(1), setrlimit(2), sigaction(2), sysctl(8)
HISTORY
A core file format appeared in Version 6 AT&T UNIX.
BSD
November 22, 2012 BSD