From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: vfs whitebox test
Date: 25 Nov 2003 12:59:39 -0700 [thread overview]
Message-ID: <1069790379.2302.20.camel@patrh9> (raw)
In-Reply-To: <1069780337.2731.3.camel@patrh9>
> > gdb /usr/src/linux/vmlinux /proc/kcore
> >
> > ... "all the structures in the kernel to be read, but no local variables
> > [also] not possible to change values or call kernel functions ..."
> ...
> grep -i CONFIG.DEBUG_INFO `find . -name 'Kconfig'`
`make xconfig` --> "Kernel hacking" forces the pair:
+ CONFIG_DEBUG_KERNEL=y
+ CONFIG_DEBUG_INFO=y
Also I accepted the suggestions:
+ CONFIG_DEBUG_SLAB=y
+ CONFIG_MAGIC_SYSRQ=y
While still testing at random in hope of discovering something relevant,
I should also try the slow DEBUG_PAGEALLOC, also DEBUG_STACKOVERFLOW.
Pat LaVarre
next prev parent reply other threads:[~2003-11-25 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 23:29 vfs whitebox test Pat LaVarre
2003-11-25 15:46 ` Pat LaVarre
2003-11-25 17:04 ` Pat LaVarre
2003-11-25 17:06 ` Randy.Dunlap
2003-11-25 17:12 ` Pat LaVarre
2003-11-25 19:59 ` Pat LaVarre [this message]
2003-11-25 17:09 ` Randy.Dunlap
2003-11-25 17:33 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 19:14 Pat LaVarre
2003-12-05 18:12 ` Pat LaVarre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1069790379.2302.20.camel@patrh9 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox