public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17890] New: gdb needs to punt when it sees a dwarf line table version it doesn't understand
Date: Tue, 27 Jan 2015 22:42:00 -0000	[thread overview]
Message-ID: <bug-17890-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17890

            Bug ID: 17890
           Summary: gdb needs to punt when it sees a dwarf line table
                    version it doesn't understand
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

I'm currently adding support for Two Level Linetables,
and noticed gdb going into an infinite loop on programs
compiled with them.
http://wiki.dwarfstd.org/index.php?title=TwoLevelLineTables

There are two bugs here:

1) gdb should punt when it sees a line table header version it doesn't
   understand.  The format could be different, there could be new fields
   or whatever, and blindly continuing is asking for trouble.

2) with the line table errantly read some fields like lh->range are
   getting a value of zero resulting in a SIGFPE (divide-by-zero).
   GDB's handling of SIGFPE it to mark the event with the async handler
   and return.  Eh?
   This results in an infinite loop of SIGFPE->handle_sigfpe->SIGFPE
   ->handle_sigfpe->...
   [filed as a separate bug, the number to be recorded once I know it]

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-01-27 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 22:42 dje at google dot com [this message]
2015-01-29 18:31 ` [Bug symtab/17890] " cvs-commit at gcc dot gnu.org
2015-01-30  9:18 ` cvs-commit at gcc dot gnu.org
2024-01-11 18:51 ` ssbssa at sourceware 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=bug-17890-4717@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: link
Be 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).