Re: [pushed] gdb/mi: consistently notify user when GDB/MI client uses -thread-select

Jan Vrany via Gdb-patches
2022-03-23T16:10:23Z

On Wed, 2022-03-23 at 11:16 -0400, Simon Marchi wrote:
> > I gave it a go but I'm sorry: everything seem to work as expected
> > here. I do not get "[Switching to thread 1 (process 1891548)]" message
> > on CLI when -thread-select already selected thread.
>
> Ok, strange.
>
> > I must be doing something differently. What commit is failing for you?
> > What's your ./configure incantation?
>
> My configure arguments are:
>
> 'CC=ccache gcc-11' 'CXX=ccache g++-11' '--disable-binutils' '--disable-gold' '--disable-ld' '--disable-gprof' '--disable-gas' '--with-guile' 'CFLAGS=-g3 -O0
> -fdiagnostics-color=always -fmax-errors=1 -fsanitize=address' 'CXXFLAGS=-std=c++11 -g3 -O0 -fdiagnostics-color=always -fmax-errors=1 -fsanitize=address -
> D_GLIBCXX_DEBUG=1 -D_GLIBCXX_DEBUG_PEDANTIC=1 -D_GLIBCXX_SANITIZE_VECTOR=1' 'LDFLAGS=-fuse-ld=lld -fsanitize=address' '--prefix=/usr' '--enable-ubsan' '--
> with-python=python3' '--with-debuginfod' '--enable-silent-rules' '--enable-werror'
>

Thanks! Now it is failing for me too!
I just recompiled GDB using the above command. I'll have a
look tomorrow.

Jan

>
> > I'm happy to sit down with you and have a closer look at this, maybe using
> > IRC or something.
>
> I'll try to dig deeper on my side first, thanks.
>
> Simon