public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30297] New: abg-dwarf-reader.cc:11251: execution should not have reached this point!
Date: Fri, 31 Mar 2023 17:00:13 +0000	[thread overview]
Message-ID: <bug-30297-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30297
           Summary: abg-dwarf-reader.cc:11251: execution should not have
                    reached this point!
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: woodard at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

With the latest trunk:

$ fedabipkgdiff --self-compare -a --from fc37 gcc-gdc

This is a new one that I haven't seen before:
Comparing the ABI of binaries between gcc-gdc-12.2.1-4.fc37.x86_64.rpm and
gcc-gdc-12.2.1-4.fc37.x86_64.rpm:

in compare_dies at: ../../../libabigail/src/abg-dwarf-reader.cc:11251:
execution should not have reached this point!

---

Well evidently it did. ;-)

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

             reply	other threads:[~2023-03-31 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 17:00 woodard at redhat dot com [this message]
2023-03-31 17:02 ` [Bug default/30297] " woodard at redhat dot com
2023-04-11 15:40 ` dodji at redhat dot com

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-30297-9487@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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).