Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: tromey@redhat.com
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
	        Christian Thalinger <Christian.Thalinger@sun.com>
Subject: Re: [patch] Fix Darwin breakage
Date: Fri, 14 Aug 2009 19:15:00 -0000	[thread overview]
Message-ID: <8ac60eac0908141209p7c457259h5ce40c7627e81ce5@mail.gmail.com> (raw)
In-Reply-To: <m3tz0ai6yf.fsf@fleche.redhat.com>

On Fri, Aug 14, 2009 at 11:30 AM, Tom Tromey<tromey@redhat.com> wrote:

> The idea seems reasonable enough to me, but I don't really understand
> all the implications of it.  If we need special treatment here, why not
> in all the other places that use ALL_OBJSECTIONS and the like?

Good question.

I looked in gcore.c, and it looks like it should similarly skip
OBJF_NOT_MAPPED objfiles.

In main.c, I am not sure, but possibly.

In printcmd.c, it's already skipping some (but not all!):

  ALL_OBJSECTIONS (objfile, osect)
  {
    /* Only process each object file once, even if there's a separate
       debug file.  */
    if (objfile->separate_debug_objfile_backlink)
      continue;

In spu-tdep.c and symfile.c all uses have to do with overlays,
and I *think* they should similarly skip.

On Fri, Aug 14, 2009 at 11:32 AM, Tom Tromey<tromey@redhat.com> wrote:

> I think you probably would also need to do this in
> symbol_file_add_with_addrs_or_offsets.

Right, that's what '*' in 'symbol_file_add*' was supposed to convey.
Perhaps I should have used regexp instead of shell glob :-)

Thanks,
-- 
Paul Pluzhnikov


  reply	other threads:[~2009-08-14 19:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 16:32 Paul Pluzhnikov
2009-08-14 17:56 ` Paul Pluzhnikov
2009-08-14 19:09   ` Tom Tromey
2009-08-14 18:32 ` Tom Tromey
2009-08-14 19:15   ` Paul Pluzhnikov [this message]
2009-08-18 12:24 ` Christian Thalinger
2009-08-18 16:17   ` Paul Pluzhnikov
2009-08-20 17:01     ` Christian Thalinger
2009-08-20 17:09       ` Paul Pluzhnikov
2009-08-20 17:16         ` Christian Thalinger
2009-08-21 11:30         ` Christian Thalinger

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=8ac60eac0908141209p7c457259h5ce40c7627e81ce5@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=Christian.Thalinger@sun.com \
    --cc=gdb-patches@sourceware.org \
    --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