public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/95574] line table entry in sequence with address after sequence Date: Mon, 08 Jun 2020 09:36:43 +0000 [thread overview] Message-ID: <bug-95574-4-WLppiTQ5fF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95574-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95574 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- Gdb currently silently ignores the offending entry. I've filed a gdb PR, PR26092 - "Complain about contradictory DW_LNE_end_sequence marker" to complain about this ( https://sourceware.org/bugzilla/show_bug.cgi?id=26092 ).
next prev parent reply other threads:[~2020-06-08 9:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 9:18 [Bug debug/95574] New: " vries at gcc dot gnu.org 2020-06-08 9:27 ` [Bug debug/95574] " vries at gcc dot gnu.org 2020-06-08 9:35 ` vries at gcc dot gnu.org 2020-06-08 9:36 ` vries at gcc dot gnu.org [this message] 2020-07-07 13:40 ` vries at gcc dot gnu.org 2020-07-07 13:44 ` vries at gcc dot gnu.org 2020-07-07 14:03 ` vries at gcc dot gnu.org 2020-07-07 14:13 ` 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-95574-4-WLppiTQ5fF@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).