From: Tom Tromey <tom@tromey.com>
To: Dmitry Antipov <dantipov@nvidia.com>
Cc: GDB Development <gdb@sourceware.org>, Yao Qi <yao.qi@linaro.org>
Subject: Re: Dummy leftover in d3037ba6a398d37585b3d34ff9ed439848ba98a1
Date: Wed, 18 Oct 2017 15:35:00 -0000 [thread overview]
Message-ID: <87po9ko4e1.fsf@tromey.com> (raw)
In-Reply-To: <6cfccaca-31c2-d994-f8c1-fda3f72224e3@nvidia.com> (Dmitry Antipov's message of "Tue, 17 Oct 2017 15:00:37 +0300")
>>>>> "Dmitry" == Dmitry Antipov <dantipov@nvidia.com> writes:
Dmitry> IIUC this gdb_assert () is no longer needed:
[...]
Dmitry> - gdb_assert (read != NULL);
Yes, that's correct; but FWIW this is already fixed in git master.
Tom
prev parent reply other threads:[~2017-10-18 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:01 Dmitry Antipov
2017-10-18 15:35 ` 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=87po9ko4e1.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dantipov@nvidia.com \
--cc=gdb@sourceware.org \
--cc=yao.qi@linaro.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: 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