public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/8300] no local symbol information within nested or nesting procedures Date: Thu, 29 Jul 2010 19:43:00 -0000 [thread overview] Message-ID: <20100729194334.5529.qmail@sourceware.org> (raw) In-Reply-To: <20030429130800.8300.stolfi@ic.unicamp.br> ------- Additional Comments From tromey at redhat dot com 2010-07-29 19:43 ------- I looked at this a little more deeply today, with some advice from Roland. The problem in this case is that the 'subproc' function does not reference any variables from its enclosing context. So, gcc does not emit DW_AT_static_link. I think the right thing to do in this case is to throw an error for any variable from the outer function that requires a frame. If you add a mention of 'w' to 'subproc', then the DWARF looks better. However, gdb doesn't ever use DW_AT_static_link, so if you get the right answer it is purely by accident. -- http://sourceware.org/bugzilla/show_bug.cgi?id=8300 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-07-29 19:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030429130800.8300.stolfi@ic.unicamp.br> 2009-04-22 14:20 ` jan dot kratochvil at redhat dot com 2010-02-04 21:11 ` tromey at redhat dot com 2010-07-29 19:43 ` tromey at redhat dot com [this message] [not found] <bug-8300-4717@http.sourceware.org/bugzilla/> 2012-07-11 13:27 ` tromey at redhat dot com 2013-02-22 16:02 ` tromey at redhat dot com
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=20100729194334.5529.qmail@sourceware.org \ --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: linkBe 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).