public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "graydon at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/23551] New: dwarf records for inlines appear incomplete Date: Wed, 24 Aug 2005 20:52:00 -0000 [thread overview] Message-ID: <20050824205103.23551.graydon@redhat.com> (raw) It appears that inlined_subroutine dwarf records are not always generated for inlined functions, and when they are generated the formal_parameter records of the inlined_subroutine do not always have location records. I have prepared 6 files (2 per case) demonstrating 3 different minimal cases. In each case, the .i file is the input and the .dump file is the result of running eu-readelf --debug-dump a.out. The three cases are: - formal-parameter-but-no-location: this has an inlined_subroutine record with no location attribute on the formal_parameter. the missing attribute should appear around line 77 of the dump. - no-inlined-subroutine-record: this shows that inlined_subroutines are not always generated. the missing record should appear around line 54 of the dump. - constant-formal-parameter-with-location.dump: this has a record in the form I would expect to see in the previous 2 cases: lines 65-77 of the dump show both the inlined_subroutine and formal_parameter with a location attribute. Please let me know if you need more details. -- Summary: dwarf records for inlines appear incomplete Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: graydon at redhat dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i386-redhat-linux GCC host triplet: i386-redhat-linux GCC target triplet: i386-redhat-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23551
next reply other threads:[~2005-08-24 20:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-24 20:52 graydon at redhat dot com [this message] 2005-08-24 20:52 ` [Bug debug/23551] " graydon at redhat dot com 2005-08-24 20:53 ` graydon at redhat dot com 2005-08-24 20:54 ` graydon at redhat dot com 2005-08-24 20:55 ` graydon at redhat dot com 2005-08-24 20:55 ` graydon at redhat dot com 2005-08-24 20:59 ` graydon at redhat dot com 2005-08-24 21:09 ` graydon at redhat dot com 2005-08-24 21:58 ` pinskia at gcc dot gnu dot org
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=20050824205103.23551.graydon@redhat.com \ --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).