Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] fix exp/12117
Date: Wed, 13 Oct 2010 19:04:00 -0000	[thread overview]
Message-ID: <m3r5ftap9l.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTimyKxoOVrHAnKT7ueWqWyQ+tVE_k1NJrr7gX+3Q@mail.gmail.com>	(Doug Evans's message of "Wed, 13 Oct 2010 11:55:25 -0700")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> a) it seems like it's not just c/v, e.g., it's also the address space
Doug> [and perhaps here's a case where there are more bugs in this area :-)]

Yeah.  Actually, this one seems like it could cause real problems
somewhere.

Doug> b) it seems odd to have to build such types on the fly
Doug> [I can imagine a proliferation of such objects that aren't attached to
Doug> anything concrete in the debug info, and just cause confusion]

I'm not sure I understand.  The qualified variants are all linked
together and allocated alongside the main_type, so we don't have to
worry about memory leaks or excess type reinstantiation.  In fact I
think the user can cause this sort of type allocation by writing "const
sometype" in an expression.

Tom


  reply	other threads:[~2010-10-13 19:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 17:53 Doug Evans
2010-10-13 18:03 ` Doug Evans
2010-10-13 18:44 ` Tom Tromey
2010-10-13 18:55   ` Doug Evans
2010-10-13 19:04     ` Tom Tromey [this message]
2010-10-13 20:55       ` Doug Evans
2010-10-13 21:10       ` Jan Kratochvil
2010-10-14  1:55         ` Doug Evans
2010-10-14  9:35           ` Jan Kratochvil
2010-10-15 17:42             ` Tom Tromey
2010-10-15 17:49               ` Jan Kratochvil
2010-10-15 17:41         ` Tom Tromey

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=m3r5ftap9l.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.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