This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/palves/step-over-thread-exit-v3.1 in repository binutils-gdb.
discards c362f6de010 Cancel execution command on thread exit, when stepping, nex [...] discards 9ec64120f32 Centralize "[Thread ...exited]" notifications discards 073828826e9 inferior::clear_thread_list always silent discards 19ac955b58d Document remote clone events, and QThreadOptions packet discards 8bd40a1250e Testcases for stepping over thread exit syscall (PR gdb/27338) discards 6c08590eac3 gdb/testsuite/lib/my-syscalls.S: Refactor new SYSCALL macro discards cb6d6b69479 Ignore failure to read PC when resuming discards 41d8d8a1e23 Report thread exit event for leader if reporting thread exi [...] discards c409f34327a Don't resume new threads if scheduler-locking is in effect discards 7a7250c96dc gdbserver: Queue no-resumed event after thread exit discards ceeac65faf9 stop_all_threads: (re-)enable async before waiting for stops discards 046405652fd gdb: clear step over information on thread exit (PR gdb/27338) discards 275675105a6 Implement GDB_THREAD_OPTION_EXIT support for native Linux discards 40de682948f Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver discards 8391b741d12 Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-ov [...] discards 3cfb5403da6 Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core discards 1b088ca3fa2 gdbserver/linux-low.cc: Ignore event_ptid if TARGET_WAITKIN [...] discards 5324dee19ed all-stop/synchronous RSP support thread-exit events discards 3f752b22e1a Add test for stepping over clone syscall discards 0ab25fe0a14 Remove gdb/19675 kfails (displaced stepping + clone) discards 20b347200e6 gdbserver: Hide and don't detach pending clone children discards f2e0e3b1186 Thread options & clone events (Linux GDBserver) discards e03129259af Thread options & clone events (native Linux) discards 1d4a11e5f8d Thread options & clone events (core + remote) discards 12919e4ce6a Avoid duplicate QThreadEvents packets discards 4faa19e92bb Support clone events in the remote protocol discards 045cb5f95c6 comments discards 3b2638cf750 Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THRE [...] new 3d5fce9fb63 Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THRE [...] new 1f0eb5b5f58 Support clone events in the remote protocol new a4afa97d40c Avoid duplicate QThreadEvents packets new 10cf06f133f Thread options & clone events (core + remote) new a52b672f905 Thread options & clone events (native Linux) new 6cff34433ec Thread options & clone events (Linux GDBserver) new cd8454230cc gdbserver: Hide and don't detach pending clone children new 39dab41284d Remove gdb/19675 kfails (displaced stepping + clone) new 7a2cd2ddcda Add test for stepping over clone syscall new ba8962fc09f all-stop/synchronous RSP support thread-exit events new f76edf890d8 gdbserver/linux-low.cc: Ignore event_ptid if TARGET_WAITKIN [...] new bc0a080a332 Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core new e0164bc3891 Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-ov [...] new 7482b6070db Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver new f2a97cd3933 Implement GDB_THREAD_OPTION_EXIT support for native Linux new e0a33253d5e gdb: clear step over information on thread exit (PR gdb/27338) new 820ba3ec461 stop_all_threads: (re-)enable async before waiting for stops new 859163afc60 gdbserver: Queue no-resumed event after thread exit new 648e6605fb6 Don't resume new threads if scheduler-locking is in effect new 025e9d1b1b9 Report thread exit event for leader if reporting thread exi [...] new 5e407d08c78 Ignore failure to read PC when resuming new 09a31034a7a gdb/testsuite/lib/my-syscalls.S: Refactor new SYSCALL macro new 7fde9d9131b Testcases for stepping over thread exit syscall (PR gdb/27338) new 42d139787c1 Document remote clone events, and QThreadOptions packet new 0f3b71f37ed inferior::clear_thread_list always silent new fb3a9c907fb Centralize "[Thread ...exited]" notifications new a2321047a01 Cancel execution command on thread exit, when stepping, nex [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (c362f6de010) \ N -- N -- N refs/heads/users/palves/step-over-thread-exit-v3.1 (a232 [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 27 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: gdb/remote.c | 77 +++++++++++++++++++++++++++++++++++++++++++++--------------- 1 file changed, 58 insertions(+), 19 deletions(-)