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] Change counted_command_line to a shared_ptr Date: Thu, 21 Sep 2017 06:48:00 -0000 [thread overview] Message-ID: <d1b0a7bfd3df05fd2009b62b19b7535bbc6555c0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d1b0a7bfd3df05fd2009b62b19b7535bbc6555c0 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: d1b0a7bfd3df05fd2009b62b19b7535bbc6555c0 Change counted_command_line to a shared_ptr This changes counted_command_line to be a typedef for std::shared_ptr and removes the associated cleanups. In the long run I believe that cmd_list_element should also be changed to use a shared_ptr. gdb/ChangeLog 2017-09-20 Tom Tromey <tom@tromey.com> * breakpoint.c (struct counted_command_line): Remove. (breakpoint_commands): Update. (alloc_counted_command_line, incref_counted_command_line) (decref_counted_command_line, do_cleanup_counted_command_line) (make_cleanup_decref_counted_command_line): Remove. (breakpoint_set_commands, commands_command_1, ~bpstats, bpstats) (bpstat_clear_actions, bpstat_do_actions_1, watchpoint_check) (bpstat_stop_status, print_one_breakpoint_location, ~breakpoint) (save_breakpoints): Update. * breakpoint.h (counted_command_line): Now a typedef to shared_ptr. (struct breakpoint) <commands>: Now a counted_command_line. (struct bpstats) <command>: Likewise.
next reply other threads:[~2017-09-21 6:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-21 6:48 sergiodj+buildbot [this message] 2017-09-21 6:50 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, branch master sergiodj+buildbot 2017-09-21 7:55 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-09-21 8:23 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-21 8:25 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-09-21 8:25 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-09-21 8:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-09-21 8:31 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-09-21 8:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-21 8:47 ` Failures on Fedora-x86_64-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=d1b0a7bfd3df05fd2009b62b19b7535bbc6555c0@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).