From: osscontribute <osscontribute@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix broken recursion detection when printing static members
Date: Wed, 25 Oct 2017 07:11:00 -0000 [thread overview]
Message-ID: <0231F3F4-6D2F-4203-84CB-09032CDEA8D1@gmail.com> (raw)
In-Reply-To: <d75b34f250c126f2c4e3bc553cdaf606@polymtl.ca>
I merged the test into test_static_members() in classes.exp. Patch has been submitted.
Thanks
Verstuurd vanaf mijn iPhone
> Op 25 okt. 2017 om 04:23 heeft Simon Marchi <simon.marchi@polymtl.ca> het volgende geschreven:
>
>> On 2017-10-24 06:55, Patrick Frants wrote:
>> The fix shrinks the stack using obstack_blank_fast() with a negative
>> value as described at the bottom of this page:
>> https://gcc.gnu.org/onlinedocs/libiberty/Extra-Fast-Growing.html
>> "You can use obstack_blank_fast with a “negative” size argument to
>> make the current object smaller. Just don’t try to shrink it beyond
>> zero length—there’s no telling what will happen if you do that.
>> Earlier versions of obstacks allowed you to use obstack_blank to
>> shrink objects. This will no longer work."
>> A unit test (gdb.cp/printstaticrecursion.exp) was added. No new
>> regression has been observed in testsuite/gdb.cp/*.exp.
>
> As mentioned in my last review, did you have a chance to see look if it was possible to improve the existing test about recursive static fields in gdb.cp/classes.exp, rather than introducing a new one?
>
> Thanks,
>
> Simon
prev parent reply other threads:[~2017-10-25 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:55 Patrick Frants
2017-10-24 10:59 ` Patrick Frants
2017-10-25 2:24 ` Simon Marchi
2017-10-25 2:23 ` Simon Marchi
2017-10-25 7:11 ` osscontribute [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=0231F3F4-6D2F-4203-84CB-09032CDEA8D1@gmail.com \
--to=osscontribute@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.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