[Bug gdb/18226] New: completion of extended-identifiers

[ratmice at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=18226

Bug ID: 18226
Summary: completion of extended-identifiers
Product: gdb
Version: HEAD
Status: NEW
Severity: minor
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: ratmice at gmail dot com

when using an input string containing a unicode character, tab completion and
the complete command complete to non-existent symbols

echo "void foo\u0f00(){} void main(){}" | gcc -g --std c99
-fextended-identifiers -x c -; gdb -quiet ./a.out -batch -ex 'complete b foo'
-ex 'complete b fooༀ'

The first complete works fine (because the input contains no
extended-identifiers)
b fooༀ

the 2nd completion starts appending all symbols to the input string
b fooༀ_DYNAMIC
b fooༀ_GLOBAL_OFFSET_TABLE_
<snip>
b fooༀfooༀ

[ratmice at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=18226

--- Comment #1 from matt rice <ratmice at gmail dot com> ---
The same thing happens with filenames when using the break completer,to
complete filenames, but works OK for the 'file' completer.

echo "void main(){}" >fooༀ.c; gcc -g --std c99 -fextended-identifiers -x c
fooༀ.c; gdb -quiet ./a.out -batch -ex 'complete file fooༀ' -ex 'complete break
fooༀ'
file fooༀ.c
break fooༀ.c
break fooༀ_DYNAMIC
break fooༀ_GLOBAL_OFFSET_TABLE_
<snip>

[palves at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=18226

Pedro Alves <palves at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com

--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
This all seems to work for me in current master. Can you confirm?

[ratmice at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=18226

matt rice <ratmice at gmail dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED

--- Comment #3 from matt rice <ratmice at gmail dot com> ---
Can confirm, didn't figure out what fixed it though, anyhow marking resolved.
(sorry, should have tested earlier when referencing this bug)