From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] Replace reread_symbols by load+free calls
Date: Thu, 25 Jun 2009 19:57:00 -0000 [thread overview]
Message-ID: <200906252058.04530.pedro@codesourcery.com> (raw)
In-Reply-To: <20090625192120.GA29930@host0.dyn.jankratochvil.net>
On Thursday 25 June 2009 20:21:20, Jan Kratochvil wrote:
> + for (so = master_so_list (); so != NULL; so = so->next)
> + if (so->objfile == objfile)
> + break;
> + if (so != NULL)
> + continue;
>
Would this work instead?
if ((objfile->flags & (OBJF_SHARED | OBJF_USERLOADED) == OBJF_SHARED))
continue;
The OBJF_USERLOADED check is to take care of the windows-nat.c
"dll-symbols" command...
Referencing to master_so_list outside of the solib files doesn't sound
right.
On Thursday 25 June 2009 20:21:20, Jan Kratochvil wrote:
> + /* FIXME: EXEC_BFD should be always referenced only through
> + SYMFILE_OBJFILE. Currently exec_bfd exists on its own and it does not
> + have to be listed among OBJECT_FILES. exec_bfd_mtime should either be
> + used or rather dropped. */
Can you elaborate on this FIXME note? exec_bfd may or not have symbols in it.
It may or not be the same bfd as symfile_objfile. Note that there are
"exec-file" and "symbol-file" separate commands. In fact, I believe,
historicaly, the "file" command that does both things at once was only
added later. Do you plan on somehow eliminating exec_bfd?
> if (reread_one)
> {
> + /* breakpoint_re_set gets called to comply with SYMFILE_DEFER_BP_RESET
> + above. */
> clear_symtab_users ();
I can't quite parse what this comment is really saying. Who calls
breakpoint_re_set? Who is complying?
--
Pedro Alves
next prev parent reply other threads:[~2009-06-25 19:57 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 [this message]
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
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=200906252058.04530.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