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] Revert "elf: Properly compute offsets of note descriptor and next note" Date: Sat, 25 Nov 2017 03:37:00 -0000 [thread overview] Message-ID: <4e25ac038efbe5293885cc75d8a3e08b23da7cc9@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 4e25ac038efbe5293885cc75d8a3e08b23da7cc9 *** Author: Simon Marchi <simon.marchi@ericsson.com> Branch: master Commit: 4e25ac038efbe5293885cc75d8a3e08b23da7cc9 Revert "elf: Properly compute offsets of note descriptor and next note" This reverts commit 650444eb540f9fd85e821567a3f943b4bc41b8be. With this patch, running the GDB test case gdb.base/auxv.exp is stuck in an infinite loop, consuming memory to the point that it renders the machine unusable. I am reverting it so we can take our time to investigate while not killing all the developers' machines.
next reply other threads:[~2017-11-25 3:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-25 3:37 sergiodj+buildbot [this message] 2017-11-25 3:37 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot 2017-11-25 3:48 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-11-25 4:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-11-25 4:11 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-11-25 4:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-25 11:20 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-25 11:44 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-11-25 12:09 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-11-25 13:18 ` Failures on Ubuntu-AArch64-m64, " 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=4e25ac038efbe5293885cc75d8a3e08b23da7cc9@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).