From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from barracuda.ebox.ca (barracuda.ebox.ca [96.127.255.19]) by sourceware.org (Postfix) with ESMTPS id DE6D33857035 for ; Fri, 25 Sep 2020 15:48:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DE6D33857035 X-ASG-Debug-ID: 1601048912-0c856e1c4449280001-fS2M51 Received: from smtp.ebox.ca (smtp.ebox.ca [96.127.255.82]) by barracuda.ebox.ca with ESMTP id otDydarVYOEceAq6 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Sep 2020 11:48:33 -0400 (EDT) X-Barracuda-Envelope-From: simon.marchi@polymtl.ca X-Barracuda-RBL-Trusted-Forwarder: 96.127.255.82 Received: from simark.localdomain (173-246-6-90.qc.cable.ebox.net [173.246.6.90]) by smtp.ebox.ca (Postfix) with ESMTP id EA786441B21; Fri, 25 Sep 2020 11:48:32 -0400 (EDT) From: Simon Marchi X-Barracuda-RBL-IP: 173.246.6.90 X-Barracuda-Effective-Source-IP: 173-246-6-90.qc.cable.ebox.net[173.246.6.90] X-Barracuda-Apparent-Source-IP: 173.246.6.90 To: gdb-patches@sourceware.org Subject: [PATCH 0/4] Add logging for event loop events Date: Fri, 25 Sep 2020 11:48:27 -0400 X-ASG-Orig-Subj: [PATCH 0/4] Add logging for event loop events Message-Id: <20200925154831.2759299-1-simon.marchi@polymtl.ca> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Barracuda-Connect: smtp.ebox.ca[96.127.255.82] X-Barracuda-Start-Time: 1601048913 X-Barracuda-Encrypted: DHE-RSA-AES256-SHA X-Barracuda-URL: https://96.127.255.19:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ebox.ca X-Barracuda-Scan-Msg-Size: 1641 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.84871 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Spam-Status: No, score=-7.8 required=5.0 tests=BAYES_00, KAM_DMARC_QUARANTINE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_SOFTFAIL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2020 15:48:46 -0000 I currently have both hands in event loop / infrun stuff, and I found it useful to add debug prints to know when the event loop invoked an event handler. I would like to propose this for upstream, so that I don't need to maintain my own patch on the side :). Simon Marchi (4): gdb: give names to event loop file handlers gdb: give names to async event/signal handlers gdb: move debug_prefixed_vprintf to gdbsupport gdb: add debug prints in event loop gdb/async-event.c | 49 +++++++++++++++++++++++----- gdb/async-event.h | 15 ++++++--- gdb/debug.c | 13 +------- gdb/debug.h | 32 ------------------ gdb/event-top.c | 67 +++++++++++++++++++++++++++++++++----- gdb/infrun.c | 5 +-- gdb/linux-nat.c | 5 +-- gdb/record-btrace.c | 2 +- gdb/record-full.c | 2 +- gdb/remote-notif.c | 2 +- gdb/remote.c | 3 +- gdb/run-on-main-thread.c | 3 +- gdb/ser-base.c | 6 ++-- gdb/top.c | 4 +++ gdb/top.h | 3 ++ gdb/tui/tui-io.c | 2 +- gdb/tui/tui-win.c | 3 +- gdbserver/linux-low.cc | 3 +- gdbserver/remote-utils.cc | 10 +++--- gdbserver/server.cc | 15 +++++++++ gdbsupport/common-debug.cc | 11 +++++++ gdbsupport/common-debug.h | 6 ++++ gdbsupport/event-loop.cc | 60 +++++++++++++++++++++++++--------- gdbsupport/event-loop.h | 54 ++++++++++++++++++++++++++++-- 24 files changed, 274 insertions(+), 101 deletions(-) delete mode 100644 gdb/debug.h -- 2.28.0