public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/26813] DW_FORM_rnglistx and DW_FORM_loclistx not fully supported Date: Wed, 03 Feb 2021 19:17:15 +0000 [thread overview] Message-ID: <bug-26813-4717-Leq0ijVlnk@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26813-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26813 --- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The gdb-10-branch branch has been updated by Simon Marchi <simark@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=908d9586a68cfbdc0a87895e946716e07ef66904 commit 908d9586a68cfbdc0a87895e946716e07ef66904 Author: Simon Marchi <simon.marchi@efficios.com> Date: Tue Feb 2 10:40:52 2021 -0500 gdb/testsuite: add .debug_rnglists tests Add tests for the various issues fixed in the previous patches. Add a new "rnglists" procedure to the DWARF assembler, to allow generating .debug_rnglists sections. A trivial change is required to support the DWARF 5 CU header layout. gdb/testsuite/ChangeLog: PR gdb/26813 * lib/dwarf.exp (_handle_DW_FORM): Handle DW_FORM_rnglistx. (cu): Generate header for DWARF 5. (rnglists): New proc. * gdb.dwarf2/rnglists-multiple-cus.exp: New. * gdb.dwarf2/rnglists-sec-offset.exp: New. Change-Id: I5b297e59c370c60cf671dec19796a6c3b9a9f632 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-03 19:17 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-29 17:30 [Bug symtab/26813] New: " zoran.zaric at amd dot com 2020-10-29 17:33 ` [Bug symtab/26813] " zoran.zaric at amd dot com 2020-10-29 18:08 ` simark at simark dot ca 2020-10-30 14:22 ` tromey at sourceware dot org 2020-10-30 15:03 ` zoran.zaric at amd dot com 2020-10-30 18:21 ` simark at simark dot ca 2020-10-30 18:22 ` simark at simark dot ca 2020-10-30 19:03 ` simark at simark dot ca 2020-10-30 21:19 ` simark at simark dot ca 2020-11-02 15:57 ` simark at simark dot ca 2021-01-20 9:26 ` mliska at suse dot cz 2021-02-02 15:42 ` cvs-commit at gcc dot gnu.org 2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org 2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org 2021-02-02 15:43 ` cvs-commit at gcc dot gnu.org 2021-02-02 15:43 ` simark at simark dot ca 2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org 2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-03 19:17 ` cvs-commit at gcc dot gnu.org 2022-05-15 12:13 ` jeanmichael.celerier at gmail dot com 2022-05-15 14:33 ` tromey at sourceware dot org 2022-05-15 14:55 ` jeanmichael.celerier at gmail dot com 2022-05-15 15:09 ` tromey at sourceware dot org 2022-05-16 1:12 ` simark at simark dot ca
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-26813-4717-Leq0ijVlnk@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).