public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johannespfau at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/60240] New: libbacktrace problems with nested functions Date: Mon, 17 Feb 2014 11:50:00 -0000 [thread overview] Message-ID: <bug-60240-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60240 Bug ID: 60240 Summary: libbacktrace problems with nested functions Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: johannespfau at gmail dot com Created attachment 32152 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32152&action=edit test case to reproduce the bug Compile the test case with "-lbacktrace -g". Actual output: test.c:17 (null) Expected output: The backtrace should contain the function name ('a') instead of null. AFAICS the problem is in read_function_entry. There's a "abbrev->has_children" check that assumes all children of a function are inlined instances of the same function. This is not true, children can also be nested functions. libbacktrace should check the "DW_AT_inline" tag here.
reply other threads:[~2014-02-17 11:50 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-60240-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).