From: Tom Tromey <tromey@adacore.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gdb-patches@sourceware.org, tromey@adacore.com
Subject: Re: Commit "Introduce ATTRIBUTE_UNUSED_RESULT and use it" breaks gdb build
Date: Wed, 06 Mar 2019 14:58:00 -0000 [thread overview]
Message-ID: <878sxsoxqt.fsf@tromey.com> (raw)
In-Reply-To: <20190306074924.lmwwwvk3ywpjkcfw@jocasta.intra> (John Darrington's message of "Wed, 6 Mar 2019 08:49:24 +0100")
>>>>> "John" == John Darrington <john@darrington.wattle.id.au> writes:
John> CXX remote-sim.o
John> /home/john/binutils-gdb/gdb/remote-sim.c: In function 'void gdbsim_target_open(const char*, int)':
John> /home/john/binutils-gdb/gdb/remote-sim.c:765:18: error: ignoring return value of 'char** gdb_argv::release()', declared with attribute warn_unused_result [-Werror=unused-result]
John> argv.release ();
John> ^
Sorry about that. I will check in a patch to fix this momentarily.
Someday I'd like gdb to either (1) get rid of remote-sim.c and talk to
the sims using the remote protocol, or (2) arrange to always compile the
bulk of remote-sim.c. (1) would be nice because it would also be more
multi-target-capable.
Tom
prev parent reply other threads:[~2019-03-06 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 7:49 John Darrington
2019-03-06 14:58 ` Tom Tromey [this message]
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=878sxsoxqt.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=john@darrington.wattle.id.au \
/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: link
Be 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