Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] Move logic out of symbol_find_demangled_name
Date: Tue, 07 Jun 2016 14:27:00 -0000	[thread overview]
Message-ID: <9b062e13-3541-b122-2da8-1c61fe7fe55b@redhat.com> (raw)
In-Reply-To: <8760tl6xbf.fsf@tromey.com>

On 06/07/2016 12:41 PM, Tom Tromey wrote:
> -  if (gsymbol->language == language_cplus
> -      || gsymbol->language == language_rust
> -      || gsymbol->language == language_auto)
> -    {
> -      demangled =
> -        gdb_demangle (mangled, DMGL_PARAMS | DMGL_ANSI);
> -      if (demangled != NULL)
> -	{
> -	  gsymbol->language = language_cplus;
> -	  return demangled;
> -	}
> -    }

Before, this would set language to language_cplus, even if the
symbol's language was Rust.

> +/* la_sniff_by_symbol for Rust.  */
> +
> +static int
> +rust_sniff_by_symbol (const char *mangled, char **demangled)
> +{
> +  *demangled = gdb_demangle (mangled, DMGL_PARAMS | DMGL_ANSI);
> +  return 1;
> +}

However, this no longer forces C++, is that intended?

Also, before we'd check whether gdb_demangle returned not-NULL,
before taking the language, but now several languages
return 1 even if gdb_demangle returns NULL:

> +/* la_sniff_by_symbol for Java.  */
> +
> +static int
> +java_sniff_by_symbol (const char *mangled, char **demangled)
> +{
> +  *demangled = java_demangle (mangled, DMGL_PARAMS | DMGL_ANSI);
> +  return 1;
> +}
> +

Seems like the first language to be consulted always wins?
Is that intended?

Thanks,
Pedro Alves


  reply	other threads:[~2016-06-07 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 14:49 [RFA 0/3] minor language cleanups Tom Tromey
2016-06-04 14:49 ` [RFA 3/3] Move logic out of symbol_find_demangled_name Tom Tromey
2016-06-06 14:15   ` Yao Qi
2016-06-07 11:41     ` Tom Tromey
2016-06-07 14:27       ` Pedro Alves [this message]
2016-06-07 15:12         ` Tom Tromey
2016-06-13 13:35           ` Pedro Alves
2016-06-17  8:28             ` Tom Tromey
2016-06-17 12:25               ` Pedro Alves
2016-06-17 12:36                 ` Tom Tromey
2016-06-17 13:50                   ` Pedro Alves
2016-06-24  3:15                     ` Tom Tromey
2016-06-07 14:03     ` Pedro Alves
2016-06-08  2:14       ` Tom Tromey
2016-06-08  4:03         ` Tom Tromey
2016-06-13 13:35           ` Pedro Alves
2016-06-17  8:41             ` Tom Tromey
2016-06-17 12:28               ` Pedro Alves
2016-06-04 14:49 ` [RFA 2/3] Move filename extensions into language_defn Tom Tromey
2016-06-06 13:23   ` Yao Qi
2016-06-06 21:04     ` Tom Tromey
2016-06-07 15:51       ` Yao Qi
2016-06-04 14:49 ` [RFA 1/3] Use VEC for filename_language_table Tom Tromey
2016-06-06 13:06   ` Yao Qi

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=9b062e13-3541-b122-2da8-1c61fe7fe55b@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=tom@tromey.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