Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: PATCH to dwarf2read.c:decode_locdesc
Date: Thu, 10 Jan 2002 11:57:00 -0000	[thread overview]
Message-ID: <20020110145805.C10383@nevyn.them.org> (raw)
In-Reply-To: <wvlelkygznq.fsf@prospero.cambridge.redhat.com>

On Thu, Jan 10, 2002 at 12:26:33PM +0000, Jason Merrill wrote:
> I noticed that even with Daniel's recent C++ improvements (thanks!), vbase
> handling was still broken with dwarf2 because dwarf2read.c still didn't
> grok the complex location expression gcc now emits.  As it happens, by a
> fluke simply adding support for the missing opcodes causes decode_locdesc
> to produce the answer gdb wants.  The dwarf2 output expects the stack to
> start with the address of the object and produce the address of the base,
> whereas in the current gdb the stack starts with 0 and produces the
> negation of whatever constant is provided, which matches the stabs output.
> 
> Of course, gdb tries to complain about the derefs twice in the process, but
> is currently muffled.
> 
> So, it's not a complete solution, but it's entirely correct and fixes
> gdb.c++/inherit.exp.
> 
> OK to commit?

[I can't approve but] thanks!  This has been stewing on my TODO list
while I fixed other things in the type code.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-10 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  4:26 Jason Merrill
2002-01-10 11:57 ` Daniel Jacobowitz [this message]
2002-01-10 14:07 ` Elena Zannoni
2002-01-11  2:13   ` Jason Merrill
2002-01-11 14:48     ` Daniel Jacobowitz

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=20020110145805.C10383@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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