Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] lookup problem in blockframe.c:inside_main_func()
Date: Tue, 07 Oct 2003 01:49:00 -0000	[thread overview]
Message-ID: <20031007014942.GA18589@nevyn.them.org> (raw)
In-Reply-To: <20031007002422.GF933@gnat.com>

On Mon, Oct 06, 2003 at 05:24:22PM -0700, Joel Brobecker wrote:
> > [First of all, what path takes you through lookup_symbol to that
> > prompt?  That shouldn't ever happen, unless it's being generated in
> > Ada-specific code...]
> 
> It is generated in ada-specific code. Just FYI, here is our ada-specific
> lookup function, which is hooked into the language vector:
> 
>     struct symbol *
>     ada_lookup_symbol ([snip])
>     { 
>       [snip]
>       n_candidates = ada_lookup_symbol_list (ada_mangle (ada_fold_name (name)),
>                                              block0, namespace, &candidates);
>       
>       if (n_candidates == 0)
>         return NULL;
>       else if (n_candidates != 1)
>         user_select_syms (candidates, n_candidates, 1);  <<<-----
>       [snip]
>     }
> 
> user_select_syms causes the menu to appear...

Oh... I see that Ada already has an interface for selecting a list of
symbols.  Another bit that doesn't belong anywhere near the
language-specific code, if you'll permit some historical ranting.  That
should be pushed out to the symtab layer.

I'll be back to that after I finish something I'm working on in
the breakpoint code, so that the list of multiple symbols is actually
useful.

> > Don't use lookup_symbol?  On David's branch there's a minsym function
> > for finding the minimal symbol associated with a mangled name.  I
> > thought it had been merged to mainline but it hasn't.  Something to do
> > the same for symbols would be reasonable, although rare.
> 
> >   Or you could
> > just use the minsym version, and then call find_pc_function.
> 
> That's a good idea, I think. Lookup the minsym.... Hmmm, let me explore
> this path. Thanks!

Follow along with the code immediately above in the same function. 
Beware, right now that minsym code may find the one which demangles to
main; but that should change.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-10-07  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 23:37 Joel Brobecker
2003-10-07  0:15 ` Daniel Jacobowitz
2003-10-07  0:24   ` Joel Brobecker
2003-10-07  1:49     ` Daniel Jacobowitz [this message]
2003-10-07  2:14       ` Joel Brobecker
2003-10-07  3:01         ` Daniel Jacobowitz
2003-10-09 14:27         ` Daniel Jacobowitz
2003-10-10 20:57           ` Joel Brobecker

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=20031007014942.GA18589@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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