Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Moller <cmoller@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: PR10687 Printing c++ class with static array (of same type) can  produce  infinite output
Date: Tue, 20 Apr 2010 20:24:00 -0000	[thread overview]
Message-ID: <4BCE0D68.2060408@redhat.com> (raw)
In-Reply-To: <m339yqgesa.fsf@fleche.redhat.com>

On 04/20/10 14:27, Tom Tromey wrote:
>>>>>> "Chris" == Chris Moller<cmoller@redhat.com>  writes:
>>>>>>              
>
> Chris>  Added yet another recursion detector (the third, so far as I noticed)
> Chris>  to cp-valprint.c.  This one detects recursing static arrays which,
> Chris>  although it comes unstuck in the same place as the 9067 recursing
> Chris>  static structs, comes unstuck in a different way and thus needs a
> Chris>  slightly different mechanism to detect.
>
> Thanks.
>
> A couple nits and then this is ok.
>
> Chris>         addr = value_address (val);
> Chris>  +
> Chris>         obstack_grow (&dont_print_statmem_obstack, (char *)&addr,
> Chris>   		sizeof (CORE_ADDR));
>
> Chris>         CHECK_TYPEDEF (type);
> Chris>  +
> Chris>         cp_print_value_fields (type, value_enclosing_type (val),
> Chris>   			value_contents_all (val),
> Chris>   			value_embedded_offset (val), addr,
>
> These two newline additions seem gratuitous.
>
> Chris>  +      struct type * target_type = TYPE_TARGET_TYPE (type);
>
> No space after the "*" here.
>
> This is ok with those changes.  Thanks.
>    

Nits fixed and patch committed.

Chris

> Tom
>    


  reply	other threads:[~2010-04-20 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  2:14 Chris Moller
2010-04-20 18:27 ` Tom Tromey
2010-04-20 20:24   ` Chris Moller [this message]
2010-06-14 16:12 ` Ulrich Weigand

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=4BCE0D68.2060408@redhat.com \
    --to=cmoller@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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