From: Paul Koning <pkoning@equallogic.com>
To: kernel-hacker@bennee.com
Cc: gdb@sources.redhat.com
Subject: Re: Gcc options for improving debugging?
Date: Wed, 19 Jul 2006 17:53:00 -0000 [thread overview]
Message-ID: <17598.28866.916402.335524@gargle.gargle.HOWL> (raw)
In-Reply-To: <1153330383.9831.82.camel@okra.transitives.com>
>>>>> "Alex" == Alex Bennee <kernel-hacker@bennee.com> writes:
Alex> Is it the inlineing that's causing the variables to get
Alex> optimised away???
No. GCC can make variables go away without any inlining. And even if
a variable isn't optimized away completely, it can become "dead" at
some point (when it is not needed in the rest of the function). When
that happens, the register gets reused but GDB doesn't necessarily
know that. So you can still see the variable but the values it
appears to have are wrong because that register now contains something
else.
paul
next prev parent reply other threads:[~2006-07-19 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 13:05 Alex Bennee
2006-07-19 13:31 ` Daniel Jacobowitz
2006-07-19 17:50 ` Alex Bennee
2006-07-19 17:53 ` Paul Koning [this message]
2006-07-20 15:21 ` Daniel Jacobowitz
2006-07-19 17:33 ` Paul Koning
2006-07-20 16:11 ` Frank Ch. Eigler
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=17598.28866.916402.335524@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=gdb@sources.redhat.com \
--cc=kernel-hacker@bennee.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