From: Weimin Pan <weimin.pan@oracle.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3 PR gdb/16959] gdb hangs in infinite recursion
Date: Mon, 26 Mar 2018 22:28:00 -0000 [thread overview]
Message-ID: <9942e026-5491-812c-2e71-9a3586b2d4eb@oracle.com> (raw)
In-Reply-To: <9dfad20dcd264844ea7208a3cbc5a949@simark.ca>
On 3/24/2018 12:51 PM, Simon Marchi wrote:
> On 2018-03-24 15:40, Wei-min Pan wrote:
>> I have fixed the first three warnings which complained the trailing
>> whitespace
>> but couldn't figure out what caused the fourth one - new blank line
>> at EOF?
>
> I think it's an extra blank line at the end of static-typedef-print.cc.
>
> Simon
Just submitted a revised patch that took out the blank line at the end of
both static-typedef-print.cc and static-typedef-print.exp.
Thanks,
Weimin
next prev parent reply other threads:[~2018-03-26 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 21:51 Weimin Pan
2018-03-24 2:41 ` Simon Marchi
2018-03-24 19:41 ` Wei-min Pan
2018-03-24 19:51 ` Simon Marchi
2018-03-26 22:28 ` Weimin Pan [this message]
2018-03-24 10:10 ` Pedro Alves
2018-03-24 12:33 ` Simon Marchi
2018-03-24 18:56 ` Wei-min Pan
2018-03-24 19:23 ` Simon Marchi
2018-03-24 19:32 ` Wei-min Pan
2018-03-24 19:48 ` Simon Marchi
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=9942e026-5491-812c-2e71-9a3586b2d4eb@oracle.com \
--to=weimin.pan@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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