Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] (Ada) fix GDB crash printing packed array
Date: Sun, 17 Feb 2019 13:34:00 -0000	[thread overview]
Message-ID: <20190217133357.GD25164@adacore.com> (raw)
In-Reply-To: <87mumwzvad.fsf@tromey.com>

> Joel>   (1) Forcing the lookup into language_c currently does not affect
> Joel>       how symbol matching is done anymore, because we look at the symbol's
> Joel>       language to determine which kind of matching should be done;
> 
> There's also this code in get_symbol_name_matcher:
> 
>   /* If currently in Ada mode, and the lookup name is wrapped in
>      '<...>', hijack all symbol name comparisons using the Ada
>      matcher, which handles the verbatim matching.  */
>   if (current_language->la_language == language_ada
>       && lookup_name.ada ().verbatim_p ())
>     return current_language->la_get_symbol_name_matcher (lookup_name);
> 
> I don't know if this could be removed, but if so it would be better to
> do so.

I was absolutely certain, looking at the new code, that we could
remove this, but unfortunately, it turns out there is a regression.

Before removing:

    (gdb) p <MixedCaseFunc>
    $1 = void^M

After:

    (gdb) p <MixedCaseFunc>
    $1 = {<text variable, no debug info>} 0x4029c6 <MixedCaseFunc>

This tells me that the function symbol wasn't found (in the debuging
info), so we used the minsym instead.  Not sure if this is because
the verbatim_p flag might be missing, or because of something else.

We'll put this on our list of things to investigate, one of these days.

> The patch looks fine to me.

Thanks! Now pushed to master.

-- 
Joel


  reply	other threads:[~2019-02-17 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10  8:21 Joel Brobecker
2019-02-15 19:49 ` Tom Tromey
2019-02-17 13:34   ` Joel Brobecker [this message]
2019-05-10 20:51 ` Pedro Franco de Carvalho
2019-05-11 17:23   ` 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=20190217133357.GD25164@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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