diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-02-21 10:46:08 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-02-21 10:46:08 +0100 |
| commit | d61933410868ff2dd52a896520a2b620d35f3615 (patch) | |
| tree | f4af087717b49eb60a913be55f189f8d53ce6fee /gdb/python/py-continueevent.c | |
| parent | 84a227694d7b97bb4d09786dcfcc3d7c0ca16d4f (diff) | |
| download | binutils-d61933410868ff2dd52a896520a2b620d35f3615.zip binutils-d61933410868ff2dd52a896520a2b620d35f3615.tar.gz binutils-d61933410868ff2dd52a896520a2b620d35f3615.tar.bz2 | |
[gdb/dap] Make dap log printing thread-safe
I read that printing from different python threads is thread-unsafe, and I
noticed that the dap log printing is used from different threads, but doesn't
take care to make the printing thread-safe.
Fix this by using a lock to access LoggingParam.log_file.
Tested on aarch64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/python/py-continueevent.c')
0 files changed, 0 insertions, 0 deletions