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] Remove a cleanup from scm-frame.c Date: Tue, 24 Apr 2018 00:19:00 -0000 [thread overview] Message-ID: <a95c7daba4c74e61ac37ffaaaa0ba49bf16e474e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT a95c7daba4c74e61ac37ffaaaa0ba49bf16e474e *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: a95c7daba4c74e61ac37ffaaaa0ba49bf16e474e Remove a cleanup from scm-frame.c This removes a cleanup from scm-frame.c, replacing it with unique_xmalloc_ptr and a new scope. I believe this also fixes a latent bug involving calling do_cleanups twice for a single cleanup. Regression tested using the gdb.guile test suite on x86-64 Fedora 26. ChangeLog 2018-04-23 Tom Tromey <tom@tromey.com> * guile/scm-frame.c (gdbscm_frame_read_var): Use gdb::unique_xmalloc_ptr.
next reply other threads:[~2018-04-24 0:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-24 0:19 sergiodj+buildbot [this message] 2018-04-24 0:19 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2018-04-24 0:20 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-04-24 0:37 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-04-24 0:37 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-24 0:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-24 0:43 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-24 0:44 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2018-04-24 0:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-04-24 0:55 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-04-24 1:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-04-24 10:05 ` Failures on Debian-s390x-native-gdbserver-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=a95c7daba4c74e61ac37ffaaaa0ba49bf16e474e@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).