[Bug gdb/30242] gdb weird one specific command with specific input not valid to run

["czgf2v at 163 dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #6 from czgf2v <czgf2v at 163 dot com> ---
I tried building gdb from source
---------------------------
$ git clone git://sourceware.org/git/binutils-gdb.git
$ sudo apt install -y texinfo bison flex

# inspired by https://bugzilla.redhat.com/show_bug.cgi?id=1526617#c5
$ cd binutils-gdb/;./configure --disable-binutils --disable-ld --disable-gold
--disable-gas --disable-sim --disable-gprof;make;make install

# the version may be same with daily build of ubuntu-support-team ppa version
code  because both has '14.0.50'
$ /usr/local/bin/gdb  --version
GNU gdb (GDB) 14.0.50.20230320-git
---------------------------




then if I directly pass command when invoking gdb, 'shell cat
~/.gdb-color-pipe' with 'thread‘ command emit syntax highlighted line, the bug
temporarily disappeared. But then type 'thread', the info still fails to emit.
---------------------------
$ gcc -gdwarf-5 -g3 -ggdb3 basic.c -o basic;/usr/bin/gdb -q -nx -nh ./basic -ex
'source ./colors_RAttab_test.gdb' -ex "br 11" -ex "start" -ex "backtrace" -ex
"thread"
....
+++shell cat ~/.gdb-color-pipe |         sed -r
"s_([^<])(\b([a-zA-Z0-9_]+::)?[a-zA-Z0-9_\.@]+)( ?)\(_\1$(tput setaf 6)$(tput
bold)\2$(tput sgr0)\4(_g" |         sed -r "s_([a-zA-Z0-9_#]*)=_$(tput setaf
2)$(tput bold)\1$(tput sgr0)=_g" |         sed -r "s_^(#[0-9]*)_$(tput setaf
1)$(tput bold)\1$(tput sgr0)_" |        --Type <RET> for more, q to quit, c to
continue without paging--
 sed -r "s_^([ \*]) ([0-9]+)_$(tput bold)$(tput setaf 6)\1 $(tput setaf
1)\2$(tput sgr0)_" |         sed -r
"s_(\.*[/A-Za-z0-9\+_\.\-]*):([0-9]+)\$_$(tput setaf 4)\1$(tput sgr0):$(tput
setaf 3)\2$(tput sgr0)_"
[Current thread is 1 (Thread 0x7ffff7d58740 (LWP 123960))]
++do-generic-colors
....
(gdb) thread
+++shell cat ~/.gdb-color-pipe |         sed -r
"s_([^<])(\b([a-zA-Z0-9_]+::)?[a-zA-Z0-9_\.@]+)( ?)\(_\1$(tput setaf 6)$(tput
bold)\2$(tput sgr0)\4(_g" |         sed -r "s_([a-zA-Z0-9_#]*)=_$(tput setaf
2)$(tput bold)\1$(tput sgr0)=_g" |         sed -r "s_^(#[0-9]*)_$(tput setaf
1)$(tput bold)\1$(tput sgr0)_" |         sed -r "s_^([ \*]) ([0-9]+)_$(tput
bold)$(tput setaf 6)\1 $(tput setaf 1)\2$(tput sgr0)_" |         sed -r
"s_(\.*[/A-Za-z0-9\+_\.\-]*):([0-9]+)\$_$(tput setaf 4)\1$(tput sgr0):$(tput
setaf 3)\2$(tput sgr0)_"
++cleanup-color-pipe
....
---------------------------




the possible bug shown in above comment still happens when run 'thread' after
the gdb prompt.

A little weird

-- 
You are receiving this mail because:
You are on the CC list for the bug.