public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 12.0.90 available for testing
Date: Thu, 31 Mar 2022 14:58:54 +0300	[thread overview]
Message-ID: <83czi272pt.fsf@gnu.org> (raw)
In-Reply-To: <4f1b387d-8b63-47d6-79aa-93b27a2cdb9d@palves.net> (message from Pedro Alves on Thu, 31 Mar 2022 10:44:21 +0100)

> Date: Thu, 31 Mar 2022 10:44:21 +0100
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
> 
> On 2022-03-31 07:21, Eli Zaretskii via Gdb-patches wrote:
> >> Date: Sat, 26 Mar 2022 20:59:04 +0300
> >> From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
> >> Cc: gdb-patches@sourceware.org
> >>
> >> Second, one of the selftests fails:
> >>
> >>   Running selftest dw2_expand_symtabs_matching.
> >>   warning: charset conversion failure for 'u8função'.
> >>   You may have the wrong value for 'set ada source-charset'.
> >>   warning: could not convert 'yfunc ' from the host encoding (CP1255) to UTF-32.
> >>   This normally should not happen, please file a bug report.
> >>
> >> AFAIU, this is because the names of these two functions are,
> >> respectively, in UTF-8 and in Latin-1, but the charset conversion
> >> thinks they are in CP1255.  Where does the test tell the conversion
> >> functions what is the source encoding?
> > 
> > Ping!  Can someone please help me debugging this selftest failure?
> > Where should I look for the definitions of the host charset used by
> > this selftest?
> 
> This is not really a failure, it's just a warning, though the message
> gdb prints sounds scary.  I chatted with Tromey about it last week, and the
> issue is that there's a unit test that always exercises a symbol with a
> latin-1 character (0xff).  I added that testcase originally, and IIRC, that
> was about making sure that the name lookup index was able to sort
> strings properly with the 0xff character, because the code
> does "ch+1" at some point in the sorting/lookup algorithm, which overflows
> in that case.
> 
> It may be that fix is to make the unit test temporarily set the
> host charset, and also to remove that "should not happen" warning, as
> I think that it should be possible to come up with such symbol names
> with escape codes, thus it's not always really a bug.

Does this test fail on GNU/Linux?  If not, can you (or someone else)
tell what is the difference between GNU/Linux and Windows for this
purpose?  Neither is using Latin-1 as the default host charset, right?

> But in nutshell, this isn't really a GDB bug, and it shouldn't block the release.

I didn't want to imply that the release should be blocked.  I'm just
trying to use the pretest for what i's intended: to find bugs and fix
them, preferably before the release.

TIA

  reply	other threads:[~2022-03-31 11:58 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  5:58 Joel Brobecker
2022-03-26 15:26 ` Eli Zaretskii
2022-03-26 15:53   ` Joel Brobecker
2022-03-26 16:15     ` Eli Zaretskii
2022-04-07 16:08       ` Tom Tromey
2022-04-07 16:12         ` Eli Zaretskii
2022-04-07 18:00           ` Joel Brobecker
2022-04-07 18:04             ` Simon Marchi
2022-04-07 19:02             ` Tom Tromey
2022-04-07 19:11               ` Joel Brobecker
2022-04-08 13:38                 ` Tom Tromey
2022-04-08 14:33                   ` Pedro Alves
2022-04-18 15:26                     ` Tom Tromey
2022-04-18 16:13                       ` Tom Tromey
2022-04-07 18:30           ` Tom Tromey
2022-04-08  6:58             ` Eli Zaretskii
2022-04-18 19:28               ` Tom Tromey
2022-03-26 17:59 ` Eli Zaretskii
2022-03-26 18:34   ` Eli Zaretskii
2022-03-26 18:51     ` Eli Zaretskii
2022-03-27  6:27       ` Eli Zaretskii
2022-03-31  6:23         ` Eli Zaretskii
2022-03-31  9:48           ` Pedro Alves
2022-03-31 11:55             ` Eli Zaretskii
2022-04-01 10:12               ` Andrew Burgess
2022-04-01 11:18                 ` Eli Zaretskii
2022-04-01 11:25                   ` Eli Zaretskii
2022-04-01 15:21                     ` Andrew Burgess
2022-04-01 16:18                       ` Eli Zaretskii
2022-04-03 13:02                         ` Hannes Domani
2022-04-03 13:34                           ` Eli Zaretskii
2022-04-03 14:03                           ` Joel Brobecker
2022-04-03 15:26                             ` Hannes Domani
2022-04-03 15:38                               ` Eli Zaretskii
2022-04-07 11:09                                 ` Eli Zaretskii
2022-04-07 18:03                                   ` Joel Brobecker
2022-04-10 19:06                                     ` Joel Brobecker
2022-04-11 11:42                                       ` Eli Zaretskii
2022-04-17 17:28                                         ` Joel Brobecker
2022-04-19 16:12                                           ` Andrew Burgess
2022-04-19 16:16                                             ` Eli Zaretskii
2022-04-20 13:26                                               ` Andrew Burgess
2022-04-20 17:11                                               ` Joel Brobecker
2022-04-20 17:30                                                 ` Eli Zaretskii
2022-04-24 15:56                                             ` Joel Brobecker
2022-04-25  8:48                                               ` Andrew Burgess
2022-04-07 18:28                                   ` Tom Tromey
2022-04-07 19:22                                   ` Pedro Alves
2022-04-08  4:04                                     ` Eli Zaretskii
2022-04-01 12:36                   ` Joel Brobecker
2022-04-01 12:50                     ` Eli Zaretskii
2022-04-01 14:12                       ` Joel Brobecker
2022-04-01 14:27                         ` Eli Zaretskii
2022-04-01 14:31                           ` Joel Brobecker
2022-04-08 14:44                             ` Pedro Alves
2022-04-08 20:05                               ` Eli Zaretskii
2022-03-27  9:55     ` Eli Zaretskii
2022-03-27  1:55   ` Simon Marchi
2022-03-27  5:20     ` Eli Zaretskii
2022-04-07 16:13       ` Tom Tromey
2022-04-07 16:39         ` Eli Zaretskii
2022-03-31  6:21   ` Eli Zaretskii
2022-03-31  9:44     ` Pedro Alves
2022-03-31 11:58       ` Eli Zaretskii [this message]
2022-03-31 12:05         ` Pedro Alves
2022-03-31 14:00           ` Eli Zaretskii
2022-04-12 14:01 ` Luis Machado
2022-04-12 17:57   ` Joel Brobecker
2022-04-13  7:36     ` Luis Machado
2022-04-13 12:19       ` Luis Machado
2022-04-13 16:20         ` Jose E. Marchesi
2022-04-17 17:33           ` Joel Brobecker
2022-04-18  1:48             ` Alan Modra
2022-04-26 13:54             ` Luis Machado
2022-04-26 14:56               ` Joel Brobecker
2022-04-26 15:15                 ` Luis Machado
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52   ` 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=83czi272pt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).