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 ,
does anybody know about where to get kernel debugger for linux kernel version 2.6.11.
I found it in oss.sgi.com.But there i have to download through ftp,which is not enabled here.
So can anybody tell where can i get kdb(kernel debugger)through http.
thanks in advance
sriram (0 Replies)
Discussion started by: sriram.ec
0 Replies
LEARN ABOUT LINUX
textdump
TEXTDUMP(4) BSD Kernel Interfaces Manual TEXTDUMP(4)
NAME
textdump -- textdump kernel dumping facility
SYNOPSIS
options KDB
options DDB
DESCRIPTION
The textdump facility allows the capture of kernel debugging information to disk in a human-readable rather than the machine-readable form
normally used with kernel memory dumps and minidumps. This representation, while less complete in that it does not capture full kernel
state, can provide debugging information in a more compact, portable, and persistent form than a traditional dump. By combining textdump
with other ddb(4) facilities, such as scripting and output capture, detailed bug information can be captured in a fully automated manner.
FORMAT
textdump data is stored in a dump partition in the same style as a regular memory dump, and will be automatically extracted by savecore(8) if
present on boot.
textdump files are stored in the tar(5) format, and consist of one or more text files, each storing a particular type of debugging output.
The following parts may be present:
ddb.txt Captured ddb(4) output, if the capture facility has been used. May be disabled by clearing the debug.ddb.textdump.do_ddb
sysctl.
config.txt Kernel configuration, if has been compiled into the kernel. May be disabled by clearing the debug.ddb.textdump.do_config
sysctl.
msgbuf.txt Kernel message buffer, including recent console output if the capture facility has been used. May be disabled by clearing the
debug.ddb.textdump.do_msgbuf sysctl.
panic.txt Kernel panic string, if the kernel panicked before the dump was generated. May be disabled by clearing the
debug.ddb.textdump.do_panic sysctl.
version.txt Kernel version string. My be disabled by clearing the debug.ddb.textdump.do_version sysctl.
Kernel textdumps may be extracted using tar(1).
CONFIGURATION
The textdump facility is enabled as part of the kernel debugger using options KDB and options DDB. By default, kernel dumps generated on
panic or via explicit requests for a dump will be regular memory dumps; however, by using the textdump set command in ddb(4), or by setting
the debug.ddb.textdump.pending sysctl to 1 using sysctl(8), it is possible to request that the next dump be a textdump.
If at the ddb(4) command line, the commands textdump set, textdump status, and textdump unset may be used to set, query, and clear the
textdump pending flag.
As with regular kernel dumps, a dump partition must be automatically or manually configured using dumpon(8).
EXAMPLES
In the following example, the script kdb.enter.panic will run when the kernel debugger is entered as a result of a panic, enable output cap-
ture, dump several useful pieces of debugging information, and then invoke panic in order to force a kernel dump to be written out followed
by a reboot:
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllock; call doadump; reset
In the following example, the script kdb.enter.witness will run when the kernel debugger is entered as a result of a witness violation,
printing lock-related information for the user:
script kdb.enter.witness=show locks
These scripts may also be configured using the ddb(8) utility.
SEE ALSO
tar(1), ddb(4), tar(5), ddb(8), dumpon(8), savecore(8), sysctl(8)
HISTORY
The textdump facility first appeared in FreeBSD 7.1.
AUTHORS
The textdump facility was created by Robert N. M. Watson.
BSD
December 24, 2008 BSD