From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch] Replace reread_symbols by load+free calls
Date: Fri, 14 Aug 2009 23:12:00 -0000 [thread overview]
Message-ID: <200908150010.00090.pedro@codesourcery.com> (raw)
In-Reply-To: <m3tz0agh3c.fsf@fleche.redhat.com>
I have to apologize too, since I dropped the conversation too.
On Friday 14 August 2009 23:34:31, Tom Tromey wrote:
> I realize you pulled this patch from consideration. But, FWIW, I tend
> to think it is a good idea, because it ensures that all the hooks and
> observers will be run identically in both cases.
I have to say that I didn't think it was a good idea, because of the
way the change ties the objfiles to solib.c, and the fact that
it makes it so that an objfile pointer becomes more volatile. That
is, with that change, all roots holding an objfile pointer need to
be crawled, while as is today, an objfile object's internals are the
business of objfile.c and symfile.c, and an objfile client can
hold a pointer across objfile rereads, while the pointer stays
valid. There were also some FIXME comments related to bfd_get_mtime
in the patch that looked like misunderstandings, and that threw
me off. Maybe I just didn't understand them. :-/
There's also this comment in the current code that makes that
suggested change scare me:
/* There are various functions like symbol_file_add,
symfile_bfd_open, syms_from_objfile, etc., which might
appear to do what we want. But they have various other
effects which we *don't* want. So we just do stuff
ourselves. (...) */
... as we'd be going in the opposite direction (the patch uses
symbol_file_add).
I wonder how much would we simplify reread_symbols by moving the
each-objfile rereading code to objfile.c, and refactor it to share code
with allocate_objfile, free_objfile, etc., and thus also making it easier
to make hooks and observers be consistent.
--
Pedro Alves
next prev parent reply other threads:[~2009-08-14 23:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 0:12 [patch] Use mmap instead of obstack_alloc for dwarf debug sections Paul Pluzhnikov
2009-05-28 1:16 ` Tom Tromey
2009-05-28 16:57 ` Paul Pluzhnikov
2009-05-30 22:36 ` Tom Tromey
2009-06-11 1:40 ` Paul Pluzhnikov
2009-06-11 1:43 ` Paul Pluzhnikov
2009-06-16 19:19 ` Tom Tromey
2009-06-16 20:43 ` Paul Pluzhnikov
2009-06-16 20:59 ` Tom Tromey
2009-06-16 21:07 ` Paul Pluzhnikov
2009-06-18 9:20 ` Ken Werner
2009-06-18 14:06 ` Paul Pluzhnikov
2009-06-18 14:11 ` Paul Pluzhnikov
2009-06-18 15:02 ` Ken Werner
2009-06-18 16:33 ` Paul Pluzhnikov
2009-06-19 7:10 ` Ken Werner
2009-06-23 15:03 ` [patch] Fix a reread_symbols regression by mmap [Re: [patch] Use mmap instead of obstack_alloc for dwarf debug sections.] Jan Kratochvil
2009-06-23 17:35 ` Paul Pluzhnikov
2009-06-23 18:08 ` Tom Tromey
2009-06-23 18:21 ` Jan Kratochvil
2009-06-23 20:00 ` Tom Tromey
2009-06-25 19:21 ` [patch] Replace reread_symbols by load+free calls Jan Kratochvil
2009-06-25 19:57 ` Pedro Alves
2009-06-25 23:25 ` Jan Kratochvil
2009-08-02 21:04 ` cancelled: " Jan Kratochvil
2009-08-14 23:09 ` Tom Tromey
2009-08-14 23:12 ` Pedro Alves [this message]
2009-08-17 15:41 ` Tom Tromey
2011-12-18 11:54 ` 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=200908150010.00090.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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