9 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
2. Red Hat
Hi, I face up a terrible problem that is for me setting up kdb or any other kernel debugger.
Little background:
I am writing linux kernel driver in C and ASM on host (real) machine that is Linux RHEL 6.0.
I run (I mean debug using printk's) that driver on virtual machine: QEMU, RHEL 6.0 (v... (1 Reply)
Discussion started by: Chrisdot
1 Replies
3. Programming
GNU insight debugger is not available now a days and it is required to debug/inspect
assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies
4. Solaris
I want to debug my csharp project on solaris. Is anyone can tell me a program or anything else for this?? (0 Replies)
Discussion started by: dConstantine
0 Replies
5. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
6. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
7. Programming
Hi,
can somebody advise on a better multiprocess debugger?
I heard with gdb we face lots of problems in multiprocess scenario
currently i am using gdb debugger for a single process multithreaded project..
since i am supposed to work on a multiprocess now, i googled and came across... (1 Reply)
Discussion started by: rvan
1 Replies
8. UNIX for Dummies Questions & Answers
hello
i'm working on cobol with unix
just want to know if there is any command in unix that related to debugger
i've been told something like anim command
i try to search for man anim
result :ERROR: Manual entry does not exist for page anim
does anyone have an answer ?
another thing ... (1 Reply)
Discussion started by: naamas03
1 Replies
9. UNIX for Advanced & Expert Users
hi,
I want to have a debugger for my kernel and
I am using kernel-2.6.11 n i am having patches
kdb-v4.4-2.6.11-common-1.bz2
kdb-v4.4-2.6.11-i386-1.bz2.
I applied both.
I did make menuconfig with options
CONFIG_KDB n CONFIG_FRAME_POINTER being set.
when i tried to compile kernel. I got an... (0 Replies)
Discussion started by: sriram.ec
0 Replies
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