public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Delayed physname computation
Date: Fri, 04 Jun 2010 22:37:00 -0000	[thread overview]
Message-ID: <m3zkzas9um.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BE9C9A0.2030605@redhat.com> (Keith Seitz's message of "Tue, 11	May 2010 14:18:24 -0700")

>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:

Keith> If you put a printf in set_die_type, you'll see that this function is
Keith> called twice (with different type structs) for the same DIE.

This part seems quite weird to me.
But maybe the only real fix for it would be two passes over the DIEs, or
something equally horrible.

Keith> Since there is no way to detect/trigger this in gdb without the
Keith> delayed physname patch, there seems little point IMO in testing
Keith> specifically for this. However it would be trivial for me to write up
Keith> a testcase for this. Just say the word.

I think a test case for this would be good, just to prevent regressions
in the case where someone tries to remove code that looks weird to them.

Both of these patches are ok.  Thanks, and sorry for the delay in
reviewing them.

Keith> +      physname = (char *) dwarf2_physname ((char *) mi->name, mi->die, cu);

It would be nice to const-correct enough so that we could remove these
casts.  I'm not asking you to do it though :-)

Tom

  reply	other threads:[~2010-06-04 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 20:23 Keith Seitz
2010-04-21  6:38 ` Jan Kratochvil
2010-04-23 23:04   ` Tom Tromey
2010-04-23 23:03 ` Tom Tromey
2010-04-23 23:34   ` Keith Seitz
2010-04-26 18:38     ` Tom Tromey
2010-05-11 21:18       ` Keith Seitz
2010-06-04 22:37         ` Tom Tromey [this message]
2010-04-25 10:33 ` Jan Kratochvil

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=m3zkzas9um.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).