public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vogt at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/68072] malformed DWARF TagVariable entry Date: Mon, 26 Oct 2015 15:40:00 -0000 [thread overview] Message-ID: <bug-68072-4-wXzO2Qh6X9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68072-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68072 --- Comment #1 from Dominik Vogt <vogt at linux dot vnet.ibm.com> --- It seems that the DWARF library is unable to handle DW_AT_specification: -- snip -- <1><7b4>: Abbrev Number: 27 (DW_TAG_variable) <7b5> DW_AT_specification: <0x8b> <7b9> DW_AT_decl_file : 13 <7ba> DW_AT_decl_line : 77 <7bb> DW_AT_location : 9 byte block: 3 0 0 0 0 0 0 4 80 (DW_OP_addr: 480) <1><8b>: Abbrev Number: 10 (DW_TAG_variable) <8c> DW_AT_name : (indirect string, offset: 0x3c4): secp256k1_nonce_function_rfc6979 <90> DW_AT_decl_file : 14 <91> DW_AT_decl_line : 104 <92> DW_AT_type : <0x98> <96> DW_AT_external : 1 <97> DW_AT_declaration : 1 -- snip -- DW_AT_name and DW_AT_type are provided by the DW_TAG_variable that the DW_AT_specification attribute is pointing to. Is that a known problem; ist there already a fix? Otherwise I can try to make a patch.
next prev parent reply other threads:[~2015-10-26 15:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-23 17:25 [Bug go/68072] New: " vogt at linux dot vnet.ibm.com 2015-10-26 15:40 ` vogt at linux dot vnet.ibm.com [this message] 2015-10-26 15:56 ` [Bug go/68072] " ian at airs dot com 2015-10-26 16:06 ` vogt at linux dot vnet.ibm.com 2015-10-26 16:11 ` vogt at linux dot vnet.ibm.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=bug-68072-4-wXzO2Qh6X9@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).