From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: don't corrupt cv_type chain
Date: Fri, 03 May 2002 20:02:00 -0000 [thread overview]
Message-ID: <20020504030256.GA15047@nevyn.them.org> (raw)
In-Reply-To: <npvga4zkhd.fsf@zwingli.cygnus.com>
On Fri, May 03, 2002 at 09:59:26PM -0500, Jim Blandy wrote:
> Yes, it is. I'll put it back.
Thanks!
> > DWARF-2 has to mutate types somewhat, certainly; but this sort of
> > smashing is avoidable and quite disgusting. There should be an
> > explicit list of things it is safe to modify, rather than the axe
> > that is replace_type. Adding a size or a a field list is
> > legitimate, but many of the other fields should not change.
>
> Isn't this, essentially, what my comment says?
<reads it again>
Yes, it is. Sorry for going off about it.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-05-04 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 17:20 Jim Blandy
2002-05-03 17:32 ` Daniel Jacobowitz
2002-05-03 19:59 ` Jim Blandy
2002-05-03 20:02 ` Daniel Jacobowitz [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=20020504030256.GA15047@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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