04-24-2019
Update:
I took the data in the attached file and put in the the main thread.
6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I am new to unix environment.
Please tell me how to do coredump analysis. Please explain clearly with example. What are the details are available in the core.
Thanks in advance (5 Replies)
Discussion started by: sip
5 Replies
2. UNIX for Advanced & Expert Users
Hello,
I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
Discussion started by: kimblebee
3 Replies
3. Solaris
in solaris 8 environment,frequently os panic happened and someone advise me check vmcore.:(
for crash dump facility can we use SUNEXPLORER data collector package including with analyse result of vmcore like ?
It may provides panic message included program counter address, perhaps
... (3 Replies)
Discussion started by: mahadib
3 Replies
4. AIX
Please tell me some methods to analyse core dump in AIX.:) (2 Replies)
Discussion started by: Mythili
2 Replies
5. Red Hat
We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file.
Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'.
Program... (0 Replies)
Discussion started by: pawankkamboj
0 Replies
6. UNIX for Dummies Questions & Answers
Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
LEARN ABOUT SUSE
utrace_attach_task
UTRACE_ATTACH_TASK(9) utrace core API UTRACE_ATTACH_TASK(9)
NAME
utrace_attach_task - attach new engine, or look up an attached engine
SYNOPSIS
struct utrace_engine * utrace_attach_task(struct task_struct * target, int flags, const struct utrace_engine_ops * ops, void * data);
ARGUMENTS
target
thread to attach to
flags
flag bits combined with OR, see below
ops
callback table for new engine
data
engine private data pointer
DESCRIPTION
The caller must ensure that the target thread does not get freed, i.e. hold a ref or be its parent. It is always safe to call this on
current, or on the child pointer in a report_clone callback. For most other cases, it's easier to use utrace_attach_pid instead.
UTRACE_ATTACH_CREATE
Create a new engine. If UTRACE_ATTACH_CREATE is not specified, you only look up an existing engine already attached to the thread.
UTRACE_ATTACH_EXCLUSIVE
Attempting to attach a second (matching) engine fails with -EEXIST.
UTRACE_ATTACH_MATCH_OPS
Only consider engines matching ops.
UTRACE_ATTACH_MATCH_DATA
Only consider engines matching data.
Calls with neither UTRACE_ATTACH_MATCH_OPS nor UTRACE_ATTACH_MATCH_DATA match the first among any engines attached to target. That means
that UTRACE_ATTACH_EXCLUSIVE in such a call fails with -EEXIST if there are any engines on target at all.
Kernel Hackers Manual 2.6. July 2010 UTRACE_ATTACH_TASK(9)