diff options
author | Luis Machado <luis.machado@linaro.org> | 2021-11-26 11:31:18 -0300 |
---|---|---|
committer | Luis Machado <luis.machado@linaro.org> | 2021-12-15 17:00:00 -0300 |
commit | 261b07488b9dfe69090e6980f6de9d0f4f3f03ca (patch) | |
tree | c962f1627fd0fa4daa203300f8fc2fc77fd0c47b /gdb/NEWS | |
parent | 4d3605c8ca92bcde848581a8ec031827c798501b (diff) | |
download | gdb-261b07488b9dfe69090e6980f6de9d0f4f3f03ca.zip gdb-261b07488b9dfe69090e6980f6de9d0f4f3f03ca.tar.gz gdb-261b07488b9dfe69090e6980f6de9d0f4f3f03ca.tar.bz2 |
New --enable-threading configure option to control use of threads in GDB/GDBserver
Add the --enable-threading configure option so multithreading can be disabled
at configure time. This is useful for statically-linked builds of
GDB/GDBserver, since the thread library doesn't play well with that setup.
If you try to run a statically-linked GDB built with threading, it will crash
when setting up the number of worker threads.
This new option is also convenient when debugging GDB in a system with lots of
threads, where the thread discovery code in GDB will emit too many messages,
like so:
[New Thread 0xfffff74d3a50 (LWP 2625599)]
If you have X threads, that message will be repeated X times.
The default for --enable-threading is "yes".
Diffstat (limited to 'gdb/NEWS')
-rw-r--r-- | gdb/NEWS | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -3,6 +3,17 @@ *** Changes since GDB 11 +* Configure changes + +--enable-threading + + Enable or disable multithreaded symbol loading. This is enabled + by default, but passing --disable-threading or --enable-threading=no + to configure will disable it. + + Disabling this can cause a performance penalty when there are a lot of + symbols to load, but is useful for debugging purposes. + * New commands maint set backtrace-on-fatal-signal on|off |