public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28004] DW_AT_ranges with form DW_FORM_sec_offset problem Date: Mon, 26 Jul 2021 16:17:46 +0000 [thread overview] Message-ID: <bug-28004-4717-8Pg7zwRlcW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28004-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28004 --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Simon Marchi from comment #6) > > I've tested a patch with both fixes on openSUSE Leap 15.2 x86_64 (gcc 7.5.0, > > using .debug_ranges), and on openSUSE Tumbleweed x86_64 (gcc 11.1.1, using > > .debug_rnglists). > > I took a look, and I agree that adding baseaddr here does not make sense, if > the goal is checking whether the range beginning is 0. > Ack. > So in all these ranges generated by gcc: > > DW_AT_name [DW_FORM_line_strp] > ("/build/gcc/src/gcc/libstdc++-v3/src/c++98/bitmap_allocator.cc") > DW_AT_comp_dir [DW_FORM_line_strp] > ("/build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++98") > DW_AT_ranges [DW_FORM_sec_offset] (0x00004b50 > [0x0000000000000000, 0x0000000000000056) > [0x00000000000a4790, 0x00000000000a479c) > [0x00000000000a47a0, 0x00000000000a47ac) > [0x00000000000a47b0, 0x00000000000a47c8) > [0x0000000000000000, 0x0000000000000026) > [0x00000000000a47d0, 0x00000000000a47e8) > [0x0000000000000000, 0x0000000000000026) > [0x000000000009916c, 0x00000000000991a1) > [0x00000000000991a1, 0x00000000000991d6) > [0x00000000000b1e10, 0x00000000000b1e5b) > [0x0000000000000000, 0x0000000000000011) > [0x0000000000000000, 0x0000000000000011) > > ... > > All those starting from 0 are just bad and should not be considered? > I guess so (The comment does mention that it's not uncommon). > > /me -> vacation for 1 week. > > Hope you have a good time! I did :) I've finally found time to work on the test-case and managed to create a dwarf assembly test-case for this (with .debug_ranges), so I'll probably submit the fix + test-case this week. [ Perhaps a .debug_rnglists version can be made easily as well, but I'll look into that after submission. ] -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-26 16:17 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-22 5:26 [Bug gdb/28004] New: " simark at simark dot ca 2021-06-22 5:26 ` [Bug gdb/28004] " simark at simark dot ca 2021-06-22 5:29 ` simark at simark dot ca 2021-06-25 7:03 ` vries at gcc dot gnu.org 2021-06-25 12:47 ` vries at gcc dot gnu.org 2021-06-25 14:23 ` vries at gcc dot gnu.org 2021-06-25 14:30 ` vries at gcc dot gnu.org 2021-06-25 21:40 ` vries at gcc dot gnu.org 2021-06-27 13:14 ` simark at simark dot ca 2021-07-26 16:17 ` vries at gcc dot gnu.org [this message] 2021-07-29 19:19 ` simark at simark dot ca 2021-07-29 21:27 ` vries at gcc dot gnu.org 2021-08-03 20:14 ` vries at gcc dot gnu.org 2021-08-04 14:19 ` vries at gcc dot gnu.org 2021-08-06 14:44 ` cvs-commit at gcc dot gnu.org 2021-08-06 16:02 ` cvs-commit at gcc dot gnu.org 2021-08-06 16:05 ` [Bug symtab/28004] " vries at gcc dot gnu.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=bug-28004-4717-8Pg7zwRlcW@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: 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).