From: Jim Blandy <jimb@redhat.com>
To: "MCG LU Fengcheng" <Fengcheng.LU@alcatel-sbell.com.cn>
Cc: <gdb@sourceware.org>
Subject: Re: Why are NOT the function parametters in the stack. They are in the register!
Date: Wed, 02 Nov 2005 18:28:00 -0000 [thread overview]
Message-ID: <vt27jbqsy4e.fsf@theseus.home.> (raw)
In-Reply-To: <7E98B33B3500C0409DBEC5C0E3FDEF120230B583@htmail.sbell.com.cn> (MCG LU Fengcheng's message of "Wed, 2 Nov 2005 14:07:26 +0800")
"MCG LU Fengcheng" <Fengcheng.LU@alcatel-sbell.com.cn> writes:
> Hello all
> In the PrintTrace, traceType and fmt are both NULL. It's impossible. I always give the valid pointer for the traceType and fmt.
Did you compile your code with optimization? Try compiling without
optimization and see if things behave more reasonably.
When the optimizer changes the program's code, it doesn't always
accurately describe to GDB what it has done. When this happens, GDB
can run into troubles finding variables' values (among other things).
prev parent reply other threads:[~2005-11-02 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 6:11 MCG LU Fengcheng
2005-11-02 13:45 ` Daniel Jacobowitz
2005-11-02 18:28 ` Jim Blandy [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=vt27jbqsy4e.fsf@theseus.home. \
--to=jimb@redhat.com \
--cc=Fengcheng.LU@alcatel-sbell.com.cn \
--cc=gdb@sourceware.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