From: Ian Lance Taylor <iant@google.com>
To: naveen yadav <yad.naveen@gmail.com>
Cc: gcc-help@gcc.gnu.org, gdb@sourceware.org
Subject: Re: Issue with GDB 7.0 on MIPS(gcc 4.4.1)
Date: Fri, 11 Nov 2011 16:31:00 -0000 [thread overview]
Message-ID: <mcrpqgyhb8e.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <CAJ8eaTyb_F41Te0JByEE9CRJhXp3qZ8QR-NPFXWgJ_tQmhgq4w@mail.gmail.com> (naveen yadav's message of "Fri, 11 Nov 2011 13:17:54 +0530")
naveen yadav <yad.naveen@gmail.com> writes:
> I am running one application and it generate core dump. When I run bt .
> (gdb) bt
> #0 wepp (gn=0x5d5f58, ef=0x5c43000, Bytes=429496729, gcOs=0x5c3408f)
> #1 CompactCollect (gn=0x5d5f58, ef=0x5c43000, Bytes=429496729, gcOs=0x5c3408f)
> ...
>
> In above case
> we got crash in wepp().
> CompactCollect () is main function and wepp() is another function
> which got called from CompactCollect ().
>
> When I check the assembly wepp() become inline.
> So i got bit surprise when i check that function parameter;s for both
> wepp() and CompactCollect () are same.
>
> So is it correct behaviour ? that calling and calle have same parameter
Without any information about the source code, I don't see how we can
tell whether having the same parameters is correct behaviour or not.
That said, it is certainly possible that the arguments of the inlined
function are not being displayed correctly. Mainline gcc has gotten
quite a bit better about debug info for inlined functions and in general
for avoiding incorrect display of variables in optimized code.
Ian
next prev parent reply other threads:[~2011-11-11 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 7:48 naveen yadav
2011-11-11 16:31 ` Ian Lance Taylor [this message]
2011-11-14 5:14 ` naveen yadav
2011-11-14 6:50 ` Ian Lance Taylor
2011-11-14 7:19 ` naveen yadav
2011-11-14 18:01 ` Ian Lance Taylor
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=mcrpqgyhb8e.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=yad.naveen@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