From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27010] abort in abg-reader.cc:1287 when running on aarch64
Date: Wed, 16 Jun 2021 17:31:04 +0000 [thread overview]
Message-ID: <bug-27010-9487-VXWzxmcdID@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27010-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27010
--- Comment #9 from Ben Woodard <woodard at redhat dot com> ---
There are two distinct asserts that seem to be triggered the ones in the
previous update were triggering at:
libabigail/src/abg-reader.cc:1366
The following three are triggering at:
libabigail/src/abg-reader.cc:1387
/usr/lib64/libnss_myhostname.so.2 from systemd-libs-248.3-1.fc34.x86_64
/usr/lib64/libsystemd.so.0.31.0 from systemd-libs-248.3-1.fc34.x86_64
/usr/lib64/libudev.so.1.7.1 from systemd-libs-248.3-1.fc34.x86_64
1348 /// Get the type declaration IR node that matches a given XML type node
ID.
1349 ///
1350 /// If no IR node has been built for this ID, this function builds the
1351 /// type declaration IR node and returns it. Subsequent invocation of
1352 /// this function with this ID will just return that ID previously
returned.
1353 ///
1354 /// @param id the XML node ID to consider.
1355 ///
1356 /// @return the type declaration for the ID given in parameter.
1357 type_base_sptr
1358 read_context::build_or_get_type_decl(const string& id,
1359 bool add_decl_to_scope)
1360 {
1361 type_base_sptr t = get_type_decl(id);
1362
1363 if (!t)
1364 {
1365 xmlNodePtr n = get_xml_node_from_id(id);
> 1366 ABG_ASSERT(n);
1367
1368 scope_decl_sptr scope;
1369 access_specifier access = no_access;
1370 if (add_decl_to_scope)
1371 {
1372 scope = get_scope_for_node(n, access);
1373 /// In some cases, if for instance the scope of 'n' is a
1374 /// namespace, get_scope_for_node() can trigger the building
1375 /// of what is underneath of the namespace, if that has not
1376 /// already been done. So after that, the IR node for 'n'
1377 /// might have been built; let's try to see if we are in
1378 /// that case. Otherwise, we'll just build the IR node for
1379 /// 'n' ourselves.
1380 if ((t = get_type_decl(id)))
1381 return t;
1382 ABG_ASSERT(scope);
1383 push_decl(scope);
1384 }
1385
1386 t = build_type(*this, n, add_decl_to_scope);
> 1387 ABG_ASSERT(t);
1388 if (is_member_type(t) && access != no_access)
1389 {
1390 ABG_ASSERT(add_decl_to_scope);
1391 decl_base_sptr d = get_type_declaration(t);
1392 ABG_ASSERT(d);
1393 set_member_access_specifier(d, access);
1394 }
1395 map_xml_node_to_decl(n, get_type_declaration(t));
1396
1397 if (add_decl_to_scope)
1398 pop_scope_or_abort(scope);
1399
1400 maybe_canonicalize_type(t, !add_decl_to_scope);
1401 }
1402 return t;
1403 }
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-16 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 3:58 [Bug default/27010] New: " woodard at redhat dot com
2020-12-04 4:16 ` [Bug default/27010] " woodard at redhat dot com
2020-12-04 18:19 ` woodard at redhat dot com
2020-12-04 18:36 ` woodard at redhat dot com
2020-12-04 18:47 ` woodard at redhat dot com
2021-04-13 20:22 ` woodard at redhat dot com
2021-04-13 21:09 ` woodard at redhat dot com
2021-06-07 23:56 ` woodard at redhat dot com
2021-06-08 17:34 ` woodard at redhat dot com
2021-06-16 17:21 ` woodard at redhat dot com
2021-06-16 17:31 ` woodard at redhat dot com [this message]
2021-09-09 14:07 ` woodard at redhat dot com
2023-05-12 14:17 ` greenwildebeest at mail dot com
2023-05-19 16:54 ` woodard 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-27010-9487-VXWzxmcdID@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).