From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>, Doug Evans <xdje42@gmail.com>
Subject: Re: [PATCH] PR gdb/21164: maint print {symbols,msymbols,psymbols} without args crash
Date: Wed, 15 Feb 2017 22:48:00 -0000 [thread overview]
Message-ID: <87tw7vnk9b.fsf@redhat.com> (raw)
In-Reply-To: <caaa55bc-33c6-b012-5e41-936a20b362b9@redhat.com> (Pedro Alves's message of "Wed, 15 Feb 2017 22:12:28 +0000")
On Wednesday, February 15 2017, Pedro Alves wrote:
> On 02/15/2017 08:15 PM, Sergio Durigan Junior wrote:
>
>> This patch fixes that. OK to apply?
>
> Can you add some tests for this, please?
Sure. I should have added them from the beginning, sorry.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-02-15 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:16 Sergio Durigan Junior
2017-02-15 22:12 ` Pedro Alves
2017-02-15 22:48 ` Sergio Durigan Junior [this message]
2017-02-15 22:54 ` Sergio Durigan Junior
2017-02-15 23:06 ` Pedro Alves
2017-02-16 0:57 ` Sergio Durigan Junior
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=87tw7vnk9b.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=xdje42@gmail.com \
/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