Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: RFC: bfd_section should not be NULL in call to prim_record_minimal_*
Date: Tue, 17 Apr 2012 14:29:00 -0000	[thread overview]
Message-ID: <4F8D7DB2.1000302@redhat.com> (raw)
In-Reply-To: <87hawiwijp.fsf@fleche.redhat.com>

On 04/17/2012 03:15 PM, Tom Tromey wrote:

> Pedro> Like in the patch below.  When testing it, I ran linespec.exp
> Pedro> first, and that revealed that msymbol_objfile had a bug in that
> Pedro> it didn't look at all the pspaces, only the current (the test
> Pedro> adds a second inferior, therefore a second pspace).  Not good
> Pedro> when you want to look up the objfile because you want to know the
> Pedro> msyms' pspace to begin with.
> 
> This seems odd to me.  And, with the split objfile stuff, it would be
> actively wrong, since a given msymbol could appear in multiple pspaces.
> Now, normally I wouldn't mention a patch that isn't checked in yet,
> but...


Indeed.

> 
> I think it would be better to pass the pspace around with the minimal
> symbol in linespec.c.  We certainly know it at the time we actually find
> the minsym, so it is just a matter of not losing the information.
> 
> Ok, I just looked at linespec.c again, and this is why there is an
> objfile in minsym_and_objfile.
> 
> Here's a totally untested patch based on this idea.


I definitely like this even more.

-- 
Pedro Alves


      reply	other threads:[~2012-04-17 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 21:14 Joel Brobecker
2012-04-16 21:14 ` [RFA/commit 1/2] Unused local variables in xcoffread.c:read_xcoff_symtab Joel Brobecker
2012-04-16 21:19   ` [RFA/commit 2/2] pspace != NULL failed assertion on ppc-aix Joel Brobecker
2012-04-18  0:43     ` Joel Brobecker
2012-04-18 10:17       ` Pedro Alves
2012-04-18 14:57         ` Joel Brobecker
2012-04-18 15:13           ` Pedro Alves
2012-04-18  0:32   ` checked in: [RFA/commit 1/2] Unused local variables in xcoffread.c:read_xcoff_symtab Joel Brobecker
2012-04-17 12:03 ` RFC: bfd_section should not be NULL in call to prim_record_minimal_* Tom Tromey
2012-04-17 15:17   ` Joel Brobecker
2012-04-17 15:23     ` Tom Tromey
2012-04-17 23:26       ` Joel Brobecker
2012-04-18 15:01         ` Tom Tromey
2012-04-18  0:24   ` Joel Brobecker
2012-04-17 12:45 ` Pedro Alves
2012-04-17 14:21   ` Tom Tromey
2012-04-17 14:29     ` Pedro Alves [this message]

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=4F8D7DB2.1000302@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.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