public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: favourite vfs globals
Date: 28 Nov 2003 14:05:31 -0700	[thread overview]
Message-ID: <1070053531.2340.40.camel@patrh9> (raw)

Which vfs globals are the most fun, in lk like 2.6.0-test11?

Pat LaVarre

P.S. I ask because:

> From: http://marc.theaimsgroup.com/?l=linux-fsdevel&m=107004461717172
> Subject:  Re: zeroes read back more often than appended
> Date:     2003-11-28 18:29:39
>
> CONFIG_DEBUG_KERNEL=y
> CONFIG_DEBUG_INFO=y
> CONFIG_DEBUG_SLAB=y
> CONFIG_MAGIC_SYSRQ=y

gdb vmlinux /proc/kcore

indeed does let me print globals that make some kind of sense. 
Specifically on my own in stunning ignorance, I notice Six things:

1) `?` suggests `help`.

2) `help` suggests `info variables`.

3) `info variables` takes minutes to complete, but writes its list out
thru tee if first you thought to tee your sudo'ed gdb.

4) `info variables vfs` completes much more quickly.

5) `print xtime` returns the same result til you `quit` and re-enter
gdb, also that result appears in between what `date +'%s %N'` prints
before and after, suggesting that this approach to gdb takes a blurry
snapshot of kernel memory and then walks us thru a stale copy of all the
bits.

6) Substituting /dev/kmem for /proc/kcore prints zero for xtime,
suggesting sym table addresses somehow not sync'ed with physical memory
in that abuse.



             reply	other threads:[~2003-11-28 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 21:05 Pat LaVarre [this message]
2003-11-28 21:22 ` favourite vfs globals Pat LaVarre
2003-11-28 21:43   ` Pat LaVarre
2003-11-28 21:51     ` Pat LaVarre
2003-11-28 22:42       ` 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=1070053531.2340.40.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