public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow non-ASCII characters in Rust identifiers
Date: Sun, 03 Apr 2022 17:17:25 +0100	[thread overview]
Message-ID: <87ee2e87l6.fsf@redhat.com> (raw)
In-Reply-To: <87y22nwxqb.fsf@tromey.com>

Tom Tromey <tom@tromey.com> writes:

>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>
> Tom> Rust 1.53 (quite a while ago now) ungated the support for non-ASCII
> Tom> identifiers.  This didn't work in gdb.  This is PR rust/20166.
>
> I'm checking this in.

Hi Tom!

I'm seeing this test fail.

 $ rustc --version
 rustc 1.59.0 (9d1b2106e 2022-02-23)

I've tested with gdb commit a723766c0e2 and 5187219460c.

Here's the output from gdb.log:

  (gdb) run 
  Starting program: /home/andrew/projects/binutils-gdb/build/gdb/testsuite/outputs/gdb.rust/unicode/unicode 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib64/libthread_db.so.1".
  
  Breakpoint 1, unicode::main () at /home/andrew/projects/binutils-gdb/build/gdb/testsuite/../../../src/gdb/testsuite/gdb.rust/unicode.rs:25
  25          println!("{}, {}", ð<U+009D><U+0095>¯, cç);        // set breakpoint here
  (gdb) print ð<U+009D><U+0095>¯
  unexpected token
  (gdb) FAIL: gdb.rust/unicode.exp: print D
  print "ð<U+009D><U+0095>¯"
  $1 = "ð\302\235\302\225¯"
  (gdb) FAIL: gdb.rust/unicode.exp: print D in string
  print 'ð<U+009D><U+0095>¯'
  Unterminated character literal
  (gdb) FAIL: gdb.rust/unicode.exp: print D as char
  print cç
  No symbol 'c' in current context
  (gdb) FAIL: gdb.rust/unicode.exp: print cc
  print 'çc'
  Unterminated character literal
  (gdb) FAIL: gdb.rust/unicode.exp: print cc as char

Do these pass for you?  Any suggestions for where to start looking?

Thanks,
Andrew


  reply	other threads:[~2022-04-03 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 23:15 Tom Tromey
2022-02-06 20:23 ` Tom Tromey
2022-04-03 16:17   ` Andrew Burgess [this message]
2022-04-03 16:51     ` Tom Tromey
2022-04-03 17:34       ` Andrew Burgess
2022-04-04  9:10         ` Andrew Burgess
2022-04-04  9:48           ` Tom Tromey

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=87ee2e87l6.fsf@redhat.com \
    --to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).