diff options
author | Andrew Burgess <aburgess@redhat.com> | 2021-11-12 10:30:27 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2021-12-22 15:02:02 +0000 |
commit | 5b0a3d62423236100bac1e77f7cc084ad9ce0271 (patch) | |
tree | 20b00bb936aa1c35f8281ddceba9d47e6d9543c3 /gdb/NEWS | |
parent | 85adb21d04edea0c7b0408a9660d5a9a5aca9ae2 (diff) | |
download | gdb-5b0a3d62423236100bac1e77f7cc084ad9ce0271.zip gdb-5b0a3d62423236100bac1e77f7cc084ad9ce0271.tar.gz gdb-5b0a3d62423236100bac1e77f7cc084ad9ce0271.tar.bz2 |
gdb: add threads debugging switch
Add new commands:
set debug threads on|off
show debug threads
Prints additional debug information relating to thread creation and
deletion.
GDB already announces when threads are created of course.... most of
the time, but sometimes threads are added silently, in which case this
debug message is the only mechanism to see the thread being added.
Also, though GDB does announce when a thread exits, it doesn't
announce when the thread object is deleted, I've added a debug message
for that.
Additionally, having message printed through the debug system will
cause the messages to be nested to an appropriate depth when other
debug sub-systems are turned on (especially things like `infrun` and
`lin-lwp`).
Diffstat (limited to 'gdb/NEWS')
-rw-r--r-- | gdb/NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -60,6 +60,10 @@ exit You can now exit GDB by using the new command "exit", in addition to the existing "quit" command. +set debug threads on|off +show debug threads + Print additional debug messages about thread creation and deletion. + * Changed commands maint packet |