From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: loody <miloody@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: some questions about kernel debugging
Date: Fri, 09 Jul 2010 13:07:00 -0000 [thread overview]
Message-ID: <20100709130708.GA13468@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTikFu0Aw81QHlNyWZ8FVbIwG-GQkZuZGntqnJ_Ji@mail.gmail.com>
On Fri, 09 Jul 2010 13:52:31 +0200, loody wrote:
> I enable kernel hacking options about kernel debugging on my mips platform.
> I can successfully connect to the target board.
> My question is:
> 1. why I cannot p/x the value of variable?
> I have enabled CONFIG_ARCH_WANT_FRAME_POINTERS and CONFIG_FRAME_POINTER
> but I still get the message which tell me "value optimized out".
> did I miss anything?
> my kernel version is 2.6.30.9?
This is not a GDB problem, you should report it to GCC (you need a minimal
reproducer for the bugreport).
The problem is Linux kernel cannot (at least could not) compile with -O0, it
requires -O2 to successfully build. -O2 was always mostly unsupported
together with -g (=debuggingo information). For -O2 -g you should use the
latest GCC - SVN HEAD best - and definitely at least 4.5 (for VTA
- var-tracking-assignments).
Besides resolving this -O2 -g problem at GCC the easy way is always to just
`disassemble' the code in GDB, guess from the code+source in which
register/memory is the value probably located and access it directly there.
Regards,
Jan
next prev parent reply other threads:[~2010-07-09 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 11:52 loody
2010-07-09 13:07 ` Jan Kratochvil [this message]
2010-07-09 15:56 ` loody
2010-07-09 16:20 ` Jan Kratochvil
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=20100709130708.GA13468@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=miloody@gmail.com \
/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