From: Tom Tromey <tromey@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Remove deprecated_sym_private
Date: Wed, 03 Feb 2010 22:09:00 -0000 [thread overview]
Message-ID: <m3y6jaott6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100203160830.GA83064@ulanbator.act-europe.fr> (Tristan Gingold's message of "Wed, 3 Feb 2010 17:08:30 +0100")
>>>>> "Tristan" == Tristan Gingold <gingold@adacore.com> writes:
Tristan> I wrote a patch that remove deprecated_sym_private, but I am
Tristan> not sure that it is worth applying it: not sure this is a real
Tristan> improvment, and I think that the private data_key could be
Tristan> shared among all symbol readers.
FWIW I agree with Daniel.
[ objfiles.h ]
Tristan> /* Per objfile data-pointers required by other GDB modules. */
Tristan> /* FIXME: kettenis/20030711: This mechanism could replace
Tristan> deprecated_sym_stab_info and deprecated_sym_private
I think this FIXME is half-obsolete now; deprecated_sym_stab_info
remains.
Tom
next prev parent reply other threads:[~2010-02-03 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:08 Tristan Gingold
2010-02-03 17:59 ` Daniel Jacobowitz
2010-02-03 22:09 ` Tom Tromey [this message]
2010-02-05 12:52 ` Tristan Gingold
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=m3y6jaott6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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