Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Tom de Vries <tdevries@suse.de>,  <gdb-patches@sourceware.org>,
	 Phil Muldoon <pmuldoon@redhat.com>,  Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb/python] Add interface to access minimal_symbols
Date: Thu, 29 Nov 2018 22:12:00 -0000	[thread overview]
Message-ID: <87d0qna5yi.fsf@tromey.com> (raw)
In-Reply-To: <39c4336d-c749-6f79-5a29-0b764fc4935e@ericsson.com> (Simon	Marchi's message of "Fri, 5 Oct 2018 00:43:12 -0400")

>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:

Simon> I think I have read (probably from Phil or Tom Tromey) that the intention was to
Simon> expose minsyms and full symbols using the same Symbol class, to avoid exposing
Simon> the fact that GDB represents symbols in different ways internally.  I don't know
Simon> if there was some concrete plans for that or if it was just at the idea stage.

I think various ideas were kicked around but nothing was really
committed to.  And, to my knowledge, nobody has really done any work in
this area.

The biggest fear, IMO, was that exposing either symbols or minimal
symbols to Python would lock us in to some undesirable API in the
future.  The basis for this fear is the (common?) belief that gdb's
internal symbol tables are not very good.  I suppose I've been hoping
for years that either somebody would finally clean things up, or that
I'd somehow get around to it.

Nowadays I tend to think we should push forward even with something that
isn't perfect.  While the worst case is pretty bad -- having to delete
some Python API and cause some chaos for users -- I imagine it won't
come to that.  And anyway Python is dynamic enough that one can usually
work around the problems.

Tom


  parent reply	other threads:[~2018-11-29 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 21:11 Tom de Vries
2018-10-05  4:43 ` Simon Marchi
2018-10-31 16:59   ` Tom de Vries
2018-11-26 11:17     ` [PING][PATCH][gdb/python] " Tom de Vries
2018-11-26 21:31     ` [PATCH][gdb/python] " Simon Marchi
2018-11-27 18:10       ` Matt Rice
2018-11-29 22:32     ` Tom Tromey
2018-11-29 22:12   ` Tom Tromey [this message]
2018-10-05  6:46 ` Eli Zaretskii
2018-10-31 17:02   ` Tom de Vries

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=87d0qna5yi.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=simon.marchi@ericsson.com \
    --cc=tdevries@suse.de \
    /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