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

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

[czgf2v at 163 dot com]

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

            Bug ID: 30242
           Summary: gdb weird one specific command with specific input not
                    valid to run
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: czgf2v at 163 dot com
  Target Milestone: 14.1

Created attachment 14756
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14756&action=edit
basic.c

my gdb config '~/dotfiles/colors.gdb'
```bash
set trace-commands on
shell test -e ~/.gdb-color-pipe && rm ~/.gdb-color-pipe
shell touch ~/.gdb-color-pipe && echo " " >> ~/.gdb-color-pipe && cat
~/.gdb-color-pipe && ls -al ~ | grep gdb
set confirm off
set logging overwrite on
set logging file ~/.gdb-color-pipe
# set logging redirect on

define hook-quit
    shell rm -f ~/.gdb-color-pipe
end

define setup-color-pipe
    set logging enabled on
end

define cleanup-color-pipe
    set logging enabled off 
end

document cleanup-color-pipe
    Disables command redirection and removes the color pipe file.
    Syntax: cleanup-color-pipe
end


define do-generic-colors
    # 1. Function names and the class they belong to
    # 2. Function argument names
    # 3. Stack frame number
    # 4. Thread id colorization
    # 5. File path and line number

    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)_"
end

#------------------------------------------------------------------------------#
# Prompt
#------------------------------------------------------------------------------#


set prompt \001\033[01;34m\002(gdb) \001\033[0m\002


#------------------------------------------------------------------------------#
# backtrace
#------------------------------------------------------------------------------#

define hook-backtrace
    setup-color-pipe
end

define hookpost-backtrace
    do-generic-colors
    cleanup-color-pipe
end

#------------------------------------------------------------------------------#
# thread
#------------------------------------------------------------------------------#

define hook-thread
    setup-color-pipe
end

define hookpost-thread
    do-generic-colors
    cleanup-color-pipe
end
```
the following code lines with "+" is debug info.
I install gdb by
```bash
sudo add-apt-repository ppa:ubuntu-support-team/gdb
sudo apt update
sudo apt install gdb
# version in ubuntu =12.1.3139.g106791196f98+22.04.20221220200615
```
then I run
```bash
$ gdb -v
GNU gdb (GDB) 14.0.50.20221220-git
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ cd /home/czg/CSAPP-3e-Solutions/site/content/gdb_repl;gcc -gdwarf-5 -g3
-ggdb3 basic.c -o basic;gdb -q -nx -nh ./basic -ex 'source
~/dotfiles/colors.gdb' -ex "br 11" -ex "start"
+shell test -e ~/.gdb-color-pipe && rm ~/.gdb-color-pipe                        
+shell touch ~/.gdb-color-pipe && echo " " >> ~/.gdb-color-pipe && cat
~/.gdb-color-pipe && ls -al ~ | grep gdb                                   
drwxr-xr-x  2 czg  czg    4096 Mar 11 11:23 .cgdb                               
-rw-rw-r--  1 czg  czg       2 Mar 18 15:57 .gdb-color-pipe                     
-rw-------  1 czg  czg    3433 Mar 18 15:03 .gdb_history                        
-rw-rw-r--  1 czg  czg   93621 Mar 17 17:08 .gdbinit                            
-rw-rw-r--  1 czg  czg   57755 Mar 14 16:47 .gdbinit_basic                      
drwxrwxr-x  2 czg  czg    4096 Mar 14 17:33 .gdbinit.d                          
-rw-rw-r--  1 czg  czg   93621 Mar 16 14:47 .gdbinit_py                         
-rw-rw-r--  1 czg  czg   92481 Mar 11 12:56 gdb.py                              
-rw-rw-r--  1 czg  czg       0 Mar 16 18:09 .gdbtxt                             
drwxr-xr-x  2 czg  czg    4096 Mar 11 11:16 .tgdb
....
+br 11
Breakpoint 1 at 0x119e: file basic.c, line 11.
+start
Temporary breakpoint 2 at 0x117c: file basic.c, line 8.
Starting program: /home/czg/CSAPP-3e-Solutions/site/content/gdb_repl/basic 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Temporary breakpoint 2, main (argc=1, argv=0x7fffffffd6a8) at basic.c:8
8           int* basic = malloc(sizeof(int));
(gdb) bt
+bt
++setup-color-pipe
+++set logging enabled on
#0  main (argc=1, argv=0x7fffffffd6a8) at basic.c:8
++do-generic-colors
+++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)_"
#0  main (argc=1, argv=0x7fffffffd6a8) at basic.c:8
++cleanup-color-pipe
+++set logging enabled off
(gdb) thread 
+thread 
++setup-color-pipe
+++set logging enabled on
[Current thread is 1 (Thread 0x7ffff7d58740 (LWP 48317))]
++do-generic-colors
+++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
+++set logging enabled off
(gdb) !echo $SHELL
+!echo $SHELL
/bin/bash
```
but if in outside shell with same command can output something which is weird.
```bash
$ echo $SHELL
/bin/bash
$ 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)_"
[Current thread is 1 (Thread 0x7ffff7d58740 (LWP 48317))]
++do-generic-colors
+++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
+++set logging enabled off
```

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

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

[czgf2v at 163 dot com]

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

--- Comment #1 from czgf2v <czgf2v at 163 dot com> ---
Created attachment 14757
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14757&action=edit
colors.gdb

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

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

[czgf2v at 163 dot com]

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

--- Comment #2 from czgf2v <czgf2v at 163 dot com> ---
Created attachment 14758
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14758&action=edit
colors.gdb

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

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

[czgf2v at 163 dot com]

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

czgf2v <czgf2v at 163 dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #14757|colors.gdb                  |colors.gdb accidentally
        description|                            |duplicate；ignore this

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

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2023-03-18

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Could you say succinctly what you think is going wrong?
I don't understand what you expect to see and how it differs
from what you do see.

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

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

[czgf2v at 163 dot com]

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

--- Comment #4 from czgf2v <czgf2v at 163 dot com> ---
sorry for so detailed information(originally for the purpose that you can
reproduce the bug so I give a lot information)


In a summary, the problem is that one shell command fails in gdb `shell cat
~/.gdb-color-pipe | sed ...`
and I wish that it can get the info indeed located in `~/.gdb-color-pipe` and
emit it in terminal.

However it fails in gdb but succeeds outside in a new tty without modifying the
file before launching a new tty.

additional information fotgot to send: bash version(which may help you to
reproduce) 
```bash
$ bash --version
bash --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
...
```

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

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

[czgf2v at 163 dot com]

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

--- Comment #5 from czgf2v <czgf2v at 163 dot com> ---
more explicitly, I wish the output in gdb
```bash
(gdb) set trace-commands off
+set trace-commands off
(gdb) bt
#0  main (argc=1, argv=0x7fffffffd888) at basic.c:8
#0  main (argc=1, argv=0x7fffffffd888) at basic.c:8
(gdb) thread 
[Current thread is 1 (Thread 0x7ffff7d58740 (LWP 5608))]
[Current thread is 1 (Thread 0x7ffff7d58740 (LWP 5608))] """""" I wish to
output this syntax highlighted line
(gdb) 
```

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

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

[czgf2v at 163 dot com]

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.

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

[czgf2v at 163 dot com]

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

czgf2v <czgf2v at 163 dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

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

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
I didn't look into it yet but I'm moving it out of WAIT.

Also I wonder if perhaps gdb should just be colorizing thread
display internally.

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

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

[czgf2v at 163 dot com]

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

--- Comment #8 from czgf2v <czgf2v at 163 dot com> ---
Yes, gdb colorizing the output at least in main branch(Sorry I forgot whether
this features exists in ubuntu 22 default gdb 12 version), although a little
different in colorized format.

Thanks, maybe thinking about the bug is a little like chasing dead ends.

My fault, using fifo and run 'cat ...' in background can solve, sorry for
having made a unnecessary bug report. 

maybe it's a bad habit to use plain text as tunnel because it would emit
nothing if nothing input(NONBLOCK).

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

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

[brobecker at gnat dot com]

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

Joel Brobecker <brobecker at gnat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brobecker at gnat dot com

--- Comment #9 from Joel Brobecker <brobecker at gnat dot com> ---
I don't think this PR qualifies as blocking for GDB 14.1 release, does it? If
not,  we should unset the Target Milestone field.

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

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

[czgf2v at 163 dot com]

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

--- Comment #10 from czgf2v <czgf2v at 163 dot com> ---
Just as [comment 7](https://sourceware.org/bugzilla/show_bug.cgi?id=30242#c7)
says, at least with `gdb 13.1` which I use now, it has built-in color
highlight. So it is fine to remove the blocking, although the milestone is not
set by me.

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

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

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|14.1                        |---

--- Comment #11 from Tom Tromey <tromey at sourceware dot org> ---
Removing the milestone.

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