From: Andrew Cagney <ac131313@cygnus.com>
To: Joshua Lamorie <jpl@xiphos.ca>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Variable locations in a loaded kernel (bsd.gdb)
Date: Mon, 27 Aug 2001 10:48:00 -0000 [thread overview]
Message-ID: <3B8A87FD.6070805@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10108271155200.8901-100000@verne.xiphos.ca>
> Gidday there,
>
> I'm trying to find how a specific variable is referenced in an
> OpenBSD 2.8 kernel. I build a kernel with symbols, and load it into gdb,
> however I can't find a way to see where a specific variable is stored
> (stack, memory, register etc...). I can't run the kernel, and when I type
> 'p function::variable' it responds with...
>
> No frame is currently executing in block scpshc_decompress.
>
> Once I have the offset, or address or whatever about the variable,
> then I can examine its value in 'ddb' after the kernel crashes.
>
> Thanks in advance. I'm running GDB 4.16.1. The 'configure'
> script doesn't let me compile version 5 on OBSD2.8.
Outch! They are both really old GDBs. Could I sugest downloading
someting more recent? The snapshots are tracking the unreleased 5.1 branch:
http://sources.redhat.com/gdb/download
Hopefully that at least builds (Changes to get GDB working on the
various BSD OSs were only committed after GDB 5 was released).
Having done this, I would add a note of caution. 4.16.1 as a GDB
version number makes me suspicious - afaik it doesn't exist! I suspect
it is in fact 4.16ob1 - an OpenBSD specific branch of GDB - and may
contain features never contributed to the FSF.
Andrew
prev parent reply other threads:[~2001-08-27 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 9:14 Joshua Lamorie
2001-08-27 9:24 ` Eli Zaretskii
2001-08-27 10:06 ` Joshua Lamorie
2001-08-27 10:48 ` Andrew Cagney [this message]
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=3B8A87FD.6070805@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jpl@xiphos.ca \
/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