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] Make parse_debug_format_options return an std::string Date: Sun, 07 Jan 2018 18:03:00 -0000 [thread overview] Message-ID: <2cc050302cd365fd28fac65d49b6c817eed74faf@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 2cc050302cd365fd28fac65d49b6c817eed74faf *** Author: Simon Marchi <simon.marchi@polymtl.ca> Branch: master Commit: 2cc050302cd365fd28fac65d49b6c817eed74faf Make parse_debug_format_options return an std::string This avoid having to manually free the return value. gdb/gdbserver/ChangeLog: * server.c (parse_debug_format_options): Return std::string. (handle_monitor_command, captured_main): Adjust.
next reply other threads:[~2018-01-07 18:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-07 18:03 sergiodj+buildbot [this message] 2018-01-07 18:03 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2018-01-07 18:07 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-01-07 18:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-01-07 18:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-01-07 18:27 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-01-07 18:33 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-01-07 23:30 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-01-08 0:00 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-01-08 0:32 ` Failures on Ubuntu-AArch32-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=2cc050302cd365fd28fac65d49b6c817eed74faf@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).