Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Empty result of "info types inner": Is this a bug?
Date: Mon, 05 Jan 2015 03:04:00 -0000	[thread overview]
Message-ID: <20150105030431.GE5445@adacore.com> (raw)
In-Reply-To: <m3lhlj7wq3.fsf@seba.sebabeach.org>

> Technically, it's a bug that the first "info types inner" didn't
> print anything, but is this a bug we're willing to accept for
> performance reasons? I want to make the case that the answer is "No."

My inclination as well, and you'll probably see in dwarf2read.c
a few added blocks of code that say "if (ada an some other langs),
add children into global scope. That was for things such as putting
a breakpoint on a nested subprogram, for instance.

-- 
Joel


  reply	other threads:[~2015-01-05  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  8:54 Doug Evans
2015-01-05  3:04 ` Joel Brobecker [this message]
2015-01-06  9:44   ` Doug Evans
2015-01-07  8:55     ` Doug Evans
2015-01-05 17:08 ` Pedro Alves

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=20150105030431.GE5445@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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