[PATCH v2 0/8] Demangle minimal symbol names in worker threads

[Philippe Waroquiers]

On Sat, 2019-05-18 at 15:00 -0600, Tom Tromey wrote:
> This is v2 of my patch series to demangle minimal symbol names in
> worker threads.
> 
> v1 was here:
> 
>     https://sourceware.org/ml/gdb-patches/2019-03/msg00211.html
> 
> I think this version addresses all the comments, in particular it adds
> a simple way to disable threading, and adds some configury.
> 
> Regression tested by the buildbot.  At one point this was failing most
> tests on the i686 builder, but I couldn't reproduce this with my own
> i686 build (on the GCC compile farm), and various checks involving
> running parts of the test suite on the buildbot using valgrind did not
> show anything.  In the end, the problem seems to have gone away
> (though there are many gdb.arch failures on i686 -- assertion failures
> in libopcodes).  So, I'm not totally sure what to make of this.
That looks like a nice startup speed improvement, will be much appreciated
when debugging big executables at work :).

HEAD:
time ../build_binutils-gdb/gdb/gdb --nx -batch -ex 'info var tructructruc' ./gdb/gdb
...
real	0m3.902s
user	0m3.068s
sys	0m0.836s

worker thread patch:
time ./gdb/gdb --nx -batch -ex 'info var tructructruc' ./gdb/gdb
...
real	0m2.379s
user	0m2.172s
sys	0m0.284s


I however do not observe much parallel CPU being used.
What type of operations will be mostly helped by parallel threads ?


One comment about 'maint set|show enable-threads' :
what is the reason to have this as a maintenance command ?
Also, maybe it would be better to have this setting being the
maximum nr of threads to use.  In some environments (e.g.
operational environments), one might want to limit the nr of threads
used by GDB.
So, maybe 'maint set enable-threads' might be replaced by something like:
   set max-gdb-threads (NUMBER | unlimited)
where unlimited means to use the max permitted by the implementation
(or similar wording as in std::thread::hardware_concurrency),
and where 0 will disable threading.

Note also that I see GDB is starting some threads by default
when guile is configured in, and 'maint set enable-threads off'
seems to not disable this type of threading.

Thanks

Philippe