public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] PR22187, infinite loop in find_abstract_instance_name Date: Sun, 24 Sep 2017 08:40:00 -0000 [thread overview] Message-ID: <52a93b95ec0771c97e26f0bb28630a271a667bd2@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 52a93b95ec0771c97e26f0bb28630a271a667bd2 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 52a93b95ec0771c97e26f0bb28630a271a667bd2 PR22187, infinite loop in find_abstract_instance_name This patch prevents the simple case of infinite recursion in find_abstract_instance_name by ensuring that the attributes being processed are not the same as the previous call. The patch also does a little cleanup, and leaves in place some changes to the nested_funcs array that I made when I wrongly thought looping might occur in scan_unit_for_symbols. PR 22187 * dwarf2.c (find_abstract_instance_name): Add orig_info_ptr and pname param. Return status. Make name const. Don't abort, return an error. Formatting. Exit if current info_ptr matches orig_info_ptr. Update callers. (scan_unit_for_symbols): Start at nesting_level of zero. Make nested_funcs an array of structs for extensibility. Formatting.
next reply other threads:[~2017-09-24 8:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-24 8:40 sergiodj+buildbot [this message] 2017-09-24 8:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-09-24 10:15 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-09-24 10:17 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-09-24 10:18 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-09-24 10:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-09-24 10:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-09-24 10:33 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-24 11:15 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-09-24 11:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-24 11:57 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-24 12:27 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-09-24 12:50 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-24 13:15 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
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=52a93b95ec0771c97e26f0bb28630a271a667bd2@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: 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).