Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Haupt <michael.haupt@oracle.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: debugging custom array types
Date: Thu, 14 Feb 2013 13:27:00 -0000	[thread overview]
Message-ID: <C76FFAFC-24F5-4355-BD2E-DEC8CB830112@oracle.com> (raw)
In-Reply-To: <87zjz8ksox.fsf@fleche.redhat.com>

Tom,

Am 13.02.2013 um 18:51 schrieb Tom Tromey <tromey@redhat.com>:
> We've made some effort over the last few years to support more of DWARF,
> but there are still holes (some mentioned in bugzilla).  Usually the
> holes are either because the implementation is very hard (the VLA work
> falls into this category) or because no compiler has ever been seen to
> emit the DWARF in question.

I see.

> Michael> DW_OP_push_object_address
> 
> This one is still unimplemented, one of the few remaining DW_OP_ holes.

OK. Is it safe to assume that the VLA work Jan keeps mentioning on this thread will eventually make it into gdb "proper" (or FSF gdb or whatever the correct name is)? Is there an idea of how long it might take?

Thanks,

Michael

-- 
Dr. Michael Haupt
Principal Member of Technical Staff
Phone: +49 331 200 7277, Fax: +49 331 200 7561
Oracle Labs
Oracle Deutschland B.V. & Co. KG, Schiffbauergasse 14, 14467 Potsdam, Germany


  reply	other threads:[~2013-02-14 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 16:51 Michael Haupt
2013-02-11 17:02 ` Jan Kratochvil
2013-02-13 10:50   ` Michael Haupt
2013-02-13 17:52     ` Tom Tromey
2013-02-14 13:27       ` Michael Haupt [this message]
2013-02-14 16:51         ` Tom Tromey
2013-02-13 17:59     ` Jan Kratochvil
2013-02-14 13:37       ` Michael Haupt
2013-02-14 13:44         ` Jan Kratochvil
2013-02-12 19:28 ` 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=C76FFAFC-24F5-4355-BD2E-DEC8CB830112@oracle.com \
    --to=michael.haupt@oracle.com \
    --cc=gdb@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