Bug 30297 - abg-dwarf-reader.cc:11251: execution should not have reached this point!
Summary: abg-dwarf-reader.cc:11251: execution should not have reached this point!
Status: NEW
Alias: None
Product: libabigail
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Dodji Seketeli
URL:
Keywords:
Depends on:
Blocks: 30334
  Show dependency tree / graph
 
Reported: 2023-03-31 17:00 UTC by Ben Woodard
Modified: 2023-04-11 15:40 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Woodard 2023-03-31 17:00:13 UTC 
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. ;-)
Comment 1 Dodji Seketeli 2023-04-11 15:40:46 UTC 
This assert is due to the fact that libabigail doesn't yet support the DW_TAG_interface_type DIE.

We ought to support this kind of DIE in the near future.