07-21-2008
There is a separate course (Kernel Internals), where this is taught. Even if i would point you to some tools (kdb, the kernel debugger for instance) - without proper training and a lot of knowledge about the inner workings of the AIX kernel you would not be able to interpret what you would see there as output, so your question doesn't make much sense.
I'd suggest that if you are really interested in such things you take the appropriate class.
I hope this helps.
bakunin
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
Hi folks,
I'm hoping someone would be charitable enough to give me a quick explanation of adb usage for analyzing core files...or point me in the right direction. A search here revealed scant results and web searches are providing me with ambiguous information.
Running Solaris.
Thanks,... (1 Reply)
Discussion started by: kristy
1 Replies
3. UNIX for Advanced & Expert Users
Hi all,
I've got a strange problem here that is not documented in AIX FAQs and tech docs, and I was wondering if somebody out there encountered the same issue or had an idea to help me out.
I'm using a script to create users with the "mkuser" command. I can set up any options I want (like... (1 Reply)
Discussion started by: dfrangidis
1 Replies
4. 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
5. UNIX for Advanced & Expert Users
Hi,
I just wanted to know is there any tool avaliable for core analysis on hp-ux. I have heard about q4 utility. But I think it is used for analysis of system crash dump and not for core dump produced by a user process.
gdb doesn't give much information unless the binary is debug-build.
... (0 Replies)
Discussion started by: shriashishpatil
0 Replies
6. 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
7. Solaris
How can we analyze a core file and determine why it was generated on a solaris system?
I know file core filename will tell us what program generated the file. But, what to do next to get more details?
Thanks, (5 Replies)
Discussion started by: Pouchie1
5 Replies
8. 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
9. 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
10. AIX
dear all,
i have p770 aix6.1
last week, the host reboot suddenly with dump. but i don't know how to analyze the dump.
I posted kdb details in the attachment.
please anybody help me.
#>kdb vmcore.0 /unix
vmcore.0 mapped from @ 700000000000000 to @ 7000001c72c0908
START ... (13 Replies)
Discussion started by: tomato00
13 Replies
LEARN ABOUT OPENSOLARIS
witness
WITNESS(4) BSD Kernel Interfaces Manual WITNESS(4)
NAME
witness -- lock validation facility
SYNOPSIS
options WITNESS
options WITNESS_KDB
options WITNESS_SKIPSPIN
DESCRIPTION
The witness module keeps track of the locks acquired and released by each thread. It also keeps track of the order in which locks are
acquired with respect to each other. Each time a lock is acquired, witness uses these two lists to verify that a lock is not being acquired
in the wrong order. If a lock order violation is detected, then a message is output to the kernel console detailing the locks involved and
the locations in question. Witness can also be configured to drop into the kernel debugger when an order violation occurs.
The witness code also checks various other conditions such as verifying that one does not recurse on a non-recursive lock. For sleep locks,
witness verifies that a new process would not be switched to when a lock is released or a lock is blocked on during an acquire while any spin
locks are held. If any of these checks fail, then the kernel will panic.
The flag that controls whether or not the kernel debugger is entered when a lock order violation is detected can be set in a variety of ways.
By default, the flag is off, but if the WITNESS_KDB kernel option is specified, then the flag will default to on. It can also be set from
the loader(8) via the debug.witness.kdb environment variable or after the kernel has booted via the debug.witness.kdb sysctl. If the flag is
set to zero, then the debugger will not be entered. If the flag is non-zero, then the debugger will be entered.
The witness code can also be configured to skip all checks on spin mutexes. By default, this flag defaults to off, but it can be turned on
by specifying the WITNESS_SKIPSPIN kernel option. The flag can also be set via the loader(8) environment variable debug.witness.skipspin.
If the variable is set to a non-zero value, then spin mutexes are skipped. Once the kernel has booted, the status of this flag can be exam-
ined but not set via the read-only sysctl debug.witness.skipspin.
The sysctl debug.witness.watch specifies the level of witness involvement in the system. A value of 1 specifies that witness is enabled. A
value of 0 specifies that witness is disabled, but that can be enabled again. This will maintain a small amount of overhead in the system.
A value of -1 specifies that witness is disabled permanently and that cannot be enabled again. The sysctl debug.witness.watch can be set via
loader(8).
The witness code also provides two extra ddb(4) commands if both witness and ddb(4) are compiled into the kernel:
show locks
Outputs the list of locks held by the current thread to the kernel console along with the filename and line number at which each lock was
last acquired by this thread.
show witness
Dump the current order list to the kernel console. The code first displays the lock order tree for all of the sleep locks. Then it displays
the lock order tree for all of the spin locks. Finally, it displays a list of locks that have not yet been acquired.
SEE ALSO
ddb(4), loader(8), sysctl(8), mutex(9)
HISTORY
The witness code first appeared in BSD/OS 5.0 and was imported from there into FreeBSD 5.0.
BUGS
The witness code currently does not handle recursion of shared sx(9) locks properly.
BSD
February 18, 2001 BSD