Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Revisit PR 16253 ("Attempt to use a type name...")
Date: Wed, 24 Jun 2015 16:54:00 -0000	[thread overview]
Message-ID: <001a113baba665ed0d0519465d3c@google.com> (raw)

Jan Kratochvil writes:
  > On Tue, 23 Jun 2015 20:39:52 +0200, Keith Seitz wrote:
  > > [But then my philosophy is "if it ain't broke, don't fix it." As far as
  > > I can tell, block_lookup_symbol is not "broke."]
  >
  > I agree, just I think a proper fix would cover also  
block_lookup_symbol().
  > But then it is questionable what is a proper fix as after this fix the  
C++
  > expression support still remains poor.  The proper GDB fix is  
C++ 'compile'
  > support being worked on.

I dunno.
We still have to keep gdb working well enough without "compile",
(other languages, core files, embedded systems)
and compile-object-load.c calls block_lookup_symbol
("compile" still relies on gdb's symbol lookup machinery).


             reply	other threads:[~2015-06-24 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 16:54 Doug Evans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-24 23:02 Doug Evans
2015-06-25 18:26 ` Keith Seitz
2015-06-16 17:54 Doug Evans
2015-06-16 21:02 ` Doug Evans
2015-06-17 15:46 ` Keith Seitz
2015-06-11 18:57 Keith Seitz
2015-06-16 16:29 ` Jan Kratochvil
2015-06-17 12:34 ` Jan Kratochvil
2015-06-17 15:50   ` Keith Seitz
2015-06-23 18:39     ` Keith Seitz
2015-06-23 19:53       ` 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=001a113baba665ed0d0519465d3c@google.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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