Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] minsyms.c: Fix switching to GNU v3 ABI
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040310150822.GA31014@nevyn.them.org> (raw)
In-Reply-To: <20040310105709.GJ25204@cygbert.vinschen.de>

On Wed, Mar 10, 2004 at 11:57:09AM +0100, Corinna Vinschen wrote:
> Hi,
> 
> I was debugging a situation, in which an C++ object file has been build
> using v3 ABI, but GDB did not recognize it and was assuming v2 ABI.  The
> target system is sh-elf, the compiler gcc 3.4.
> 
> What I found is this:
> 
> - The C++ ABI is set to v2 by default (gnu-v2-abi.c, _initialize_gnu_v2_abi).
> 
> - While reading symbols from the object file, at one point elf_symfile_read()
>   (elfread.c) is called.
> 
> - elf_symfile_read() calls elf_symtab_read() which calls
>   record_minimal_symbol() which calls prim_record_minimal_symbol_and_info().
> 
> - In prim_record_minimal_symbol_and_info(), the symbol language is set to
>   language_auto unconditionally.
> 
> - After returning from elf_symtab_read(), install_minimal_symbols() is
>   called.  At the end of install_minimal_symbols() a loop over all msymbols
>   tries to figure out if v3 ABI is used.  This is done by requesting the
>   demangeled name calling SYMBOL_DEMANGLED_NAME.
> 
> The problem is that SYMBOL_LANGUAGE is still set to language_auto and
> the demangled name hasn't been generated at this point.

This is absolutely not what should happen.

prim_record_minimal_symbol_and_info:
  SYMBOL_SET_NAMES (msymbol, (char *)name, strlen (name), objfile);

symbol_set_names:
 ->  symbol_find_demangled_name
  if (gsymbol->language == language_cplus
      || gsymbol->language == language_auto)
    {
      demangled =
        cplus_demangle (mangled, DMGL_PARAMS | DMGL_ANSI);
      if (demangled != NULL)
        {
          gsymbol->language = language_cplus;
          return demangled;
        }
    }

Please figure out why symbol_find_demangled_name has failed.  It sounds
to me like you are having a problem with leading underscores, if I
remember my sh-elf-foo correctly.

> What's especially weird is the comment above install_minimal_symbols().
> It implies that the function will try to demangle all symbols to set
> the language correctly, but the function is not doing that.  It would
> only recognize symbols which has already been demangeled but that just
> don't happen.

Comment is out of date.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] minsyms.c: Fix switching to GNU v3 ABI
Date: Wed, 10 Mar 2004 15:08:00 -0000	[thread overview]
Message-ID: <20040310150822.GA31014@nevyn.them.org> (raw)
Message-ID: <20040310150800.uPN1_LSB51I4U-cX-6kHEUUMeUgA0Q-UU7pUy00M7Q0@z> (raw)
In-Reply-To: <20040310105709.GJ25204@cygbert.vinschen.de>

On Wed, Mar 10, 2004 at 11:57:09AM +0100, Corinna Vinschen wrote:
> Hi,
> 
> I was debugging a situation, in which an C++ object file has been build
> using v3 ABI, but GDB did not recognize it and was assuming v2 ABI.  The
> target system is sh-elf, the compiler gcc 3.4.
> 
> What I found is this:
> 
> - The C++ ABI is set to v2 by default (gnu-v2-abi.c, _initialize_gnu_v2_abi).
> 
> - While reading symbols from the object file, at one point elf_symfile_read()
>   (elfread.c) is called.
> 
> - elf_symfile_read() calls elf_symtab_read() which calls
>   record_minimal_symbol() which calls prim_record_minimal_symbol_and_info().
> 
> - In prim_record_minimal_symbol_and_info(), the symbol language is set to
>   language_auto unconditionally.
> 
> - After returning from elf_symtab_read(), install_minimal_symbols() is
>   called.  At the end of install_minimal_symbols() a loop over all msymbols
>   tries to figure out if v3 ABI is used.  This is done by requesting the
>   demangeled name calling SYMBOL_DEMANGLED_NAME.
> 
> The problem is that SYMBOL_LANGUAGE is still set to language_auto and
> the demangled name hasn't been generated at this point.

This is absolutely not what should happen.

prim_record_minimal_symbol_and_info:
  SYMBOL_SET_NAMES (msymbol, (char *)name, strlen (name), objfile);

symbol_set_names:
 ->  symbol_find_demangled_name
  if (gsymbol->language == language_cplus
      || gsymbol->language == language_auto)
    {
      demangled =
        cplus_demangle (mangled, DMGL_PARAMS | DMGL_ANSI);
      if (demangled != NULL)
        {
          gsymbol->language = language_cplus;
          return demangled;
        }
    }

Please figure out why symbol_find_demangled_name has failed.  It sounds
to me like you are having a problem with leading underscores, if I
remember my sh-elf-foo correctly.

> What's especially weird is the comment above install_minimal_symbols().
> It implies that the function will try to demangle all symbols to set
> the language correctly, but the function is not doing that.  It would
> only recognize symbols which has already been demangeled but that just
> don't happen.

Comment is out of date.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2004-03-10 15:08 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Corinna Vinschen
2004-03-10 10:57 ` Corinna Vinschen
2004-03-19  0:09 ` Daniel Jacobowitz [this message]
2004-03-10 15:08   ` Daniel Jacobowitz
2004-03-10 15:55   ` Corinna Vinschen
2004-03-10 16:04     ` Daniel Jacobowitz
2004-03-10 16:16       ` Corinna Vinschen
2004-03-19  0:09         ` Corinna Vinschen
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-10 16:20           ` Daniel Jacobowitz
2004-03-19  0:09           ` Corinna Vinschen
2004-03-10 16:34             ` Corinna Vinschen
2004-03-10 16:37             ` Daniel Jacobowitz
2004-03-10 17:54               ` Corinna Vinschen
2004-03-10 18:02                 ` David Carlton
2004-03-19  0:09                   ` David Carlton
2004-03-10 18:23                 ` Corinna Vinschen
2004-03-19  0:09                   ` Corinna Vinschen
2004-03-22 17:34                   ` Corinna Vinschen
2004-03-22 17:38                     ` Corinna Vinschen
2004-03-25 20:44                   ` Jim Blandy
2004-03-26 13:57                     ` Corinna Vinschen
2004-03-26 17:54                       ` Eli Zaretskii
2004-03-28 18:28                       ` Jim Blandy
2004-03-29 11:26                         ` Corinna Vinschen
2004-03-19  0:09                 ` Daniel Jacobowitz
2004-03-10 18:20                   ` Daniel Jacobowitz
2004-03-19  0:09                 ` Corinna Vinschen
2004-03-19  0:09                 ` Ian Lance Taylor
2004-03-10 18:30                   ` Ian Lance Taylor
2004-03-19  0:09                   ` Corinna Vinschen
2004-03-10 18:46                     ` Corinna Vinschen
2004-03-10 19:02                     ` Ian Lance Taylor
2004-03-19  0:09                       ` Ian Lance Taylor
2004-03-19  0:09               ` Daniel Jacobowitz
2004-03-10 16:43             ` Corinna Vinschen
2004-03-10 16:46               ` Daniel Jacobowitz
2004-03-19  0:09                 ` Daniel Jacobowitz
2004-03-19  0:09               ` Corinna Vinschen
2004-03-19  0:09       ` Daniel Jacobowitz
2004-03-19  0:09     ` Corinna Vinschen
2004-03-19  0:09 ` Jim Blandy
2004-03-10 15:04   ` Jim Blandy
  -- strict thread matches above, loose matches on Subject: below --
2004-03-10 18:03 Michael Elizabeth Chastain
2004-03-19  0:09 ` Michael Elizabeth Chastain

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=20040310150822.GA31014@nevyn.them.org \
    --to=drow@false.org \
    --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