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 parse_expression_for_completion Date: Wed, 21 Feb 2018 16:31:00 -0000 [thread overview] Message-ID: <3eac2b654808f9e233885f910045eea9d2ca0aa0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3eac2b654808f9e233885f910045eea9d2ca0aa0 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 3eac2b654808f9e233885f910045eea9d2ca0aa0 Remove a cleanup from parse_expression_for_completion This removes a cleanup from parse_expression_for_completion, by changing various expression-completion functions to use gdb::unique_xmalloc_ptry rather than explicit malloc+free. Regression tested by the buildbot. gdb/ChangeLog 2018-02-21 Tom Tromey <tom@tromey.com> * value.h: (extract_field_op): Update. * eval.c (extract_field_op): Return a const char *. * expression.h (parse_expression_for_completion): Update. * completer.c (complete_expression): Update. (add_struct_fields): Make fieldname const. * parse.c (expout_completion_name): Now a unique_xmalloc_ptr. (mark_completion_tag, parse_exp_in_context_1): Update. (parse_expression_for_completion): Change "name" to unique_xmalloc_ptr*.
next reply other threads:[~2018-02-21 16:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-21 16:31 sergiodj+buildbot [this message] 2018-02-21 16:31 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-21 19:26 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-02-21 23:45 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-02-21 23:56 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-02-22 0:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-22 1:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-22 1:21 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-22 1:21 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-02-22 1:35 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-22 14:07 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-22 15:15 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-02-22 16:00 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-02-25 6:10 ` Failures on Debian-s390x-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=3eac2b654808f9e233885f910045eea9d2ca0aa0@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).