public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "deeprtm3997 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15011] unable to fetch function parameters
Date: Sat, 12 Jan 2013 09:31:00 -0000 [thread overview]
Message-ID: <bug-15011-4717-3osnzUR0PM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15011-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15011
--- Comment #3 from Deep <deeprtm3997 at gmail dot com> 2013-01-12 09:31:16 UTC ---
(In reply to comment #1)
> From the source it appears that this happens if a DWARF
> location expression requests the CFA for the frame, but the
> frame was found using some other unwinder:
>
> if (!frame_unwinder_is (this_frame, &dwarf2_frame_unwind)
> && !frame_unwinder_is (this_frame, &dwarf2_tailcall_frame_unwind))
> error (_("can't compute CFA for this frame"));
>
> Offhand I am not sure under what circumstances this can happen.
> Maybe if you are somehow hitting the special epilogue frame unwinder.
>
> If the .o file from which 'exec' comes is not too big, maybe
> having it would help.
Well, I am using GDB for the first time(doing an OS course), so I don't know
what is "special epilogue frame unwinder". But I am attaching exec.o, if it
helps.
Thank You.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
prev parent reply other threads:[~2013-01-12 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 19:18 [Bug gdb/15011] New: " deeprtm3997 at gmail dot com
2013-01-11 16:02 ` [Bug gdb/15011] " tromey at redhat dot com
2013-01-12 9:29 ` deeprtm3997 at gmail dot com
2013-01-12 9:31 ` deeprtm3997 at gmail dot com [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=bug-15011-4717-3osnzUR0PM@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).