Message ID | 20231004020701.260411-1-simon.marchi@polymtl.ca |
---|---|
Headers |
Return-Path: <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 8A665385C422 for <patchwork@sourceware.org>; Wed, 4 Oct 2023 02:07:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A665385C422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1696385254; bh=CLIId6nCQGjDndPhA7uD7Cn+KxPV65FVWfd8vpBWkeo=; h=To:Cc:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=X+SW9l2zans8uKUGkHNmpgY/BeeAjQKG8PWL7E0JcYlUbfnm87IVcbFzlYBt8zWKu IcHBCH19cpkw+lvLo331/E7izetF1z03hrJvchvNKTrf0GXkudxag93ejQxFFpDL2g ZvSyK93O3KAesI/xZww611QsK1VyjY03lBk7h6GE= X-Original-To: gdb-patches@sourceware.org Delivered-To: gdb-patches@sourceware.org Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 41CE6385800C for <gdb-patches@sourceware.org>; Wed, 4 Oct 2023 02:07:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 41CE6385800C Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 394273HB018709 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 3 Oct 2023 22:07:08 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 394273HB018709 Received: from simark.localdomain (modemcable238.237-201-24.mc.videotron.ca [24.201.237.238]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 4C8541E092; Tue, 3 Oct 2023 22:07:03 -0400 (EDT) To: gdb-patches@sourceware.org Cc: Simon Marchi <simon.marchi@polymtl.ca> Subject: [PATCH 0/3] Add assertion when marking the remote async flag Date: Tue, 3 Oct 2023 22:03:58 -0400 Message-ID: <20231004020701.260411-1-simon.marchi@polymtl.ca> X-Mailer: git-send-email 2.42.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Wed, 4 Oct 2023 02:07:03 +0000 X-Spam-Status: No, score=-3182.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=subscribe> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> Reply-To: Simon Marchi <simon.marchi@polymtl.ca> Errors-To: gdb-patches-bounces+patchwork=sourceware.org@sourceware.org Sender: "Gdb-patches" <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> |
Series |
Add assertion when marking the remote async flag
|
|
Message
Simon Marchi
Oct. 4, 2023, 2:03 a.m. UTC
I had this idea while reviewing this patch [1]. When marking the remote async flag, assert that the target is actually in async mode, instead of relying on an assert that comes at a later time, in the wait method. The first two patches are small preparatory refactorings, and the third one adds the assertion. [1] https://inbox.sourceware.org/gdb-patches/3d728a6e-1cb0-49c2-a4c8-0a974be39fee@simark.ca/T/#ma1903117423ae09c3574fd45ade2dd4af5280633 Simon Marchi (3): gdb: make remote_state's async token private gdb: add remote_state::{is_async_p,can_async_p} gdb: add assertion when marking the remote async flag gdb/remote.c | 93 ++++++++++++++++++++++++++++++++++------------------ 1 file changed, 62 insertions(+), 31 deletions(-) base-commit: 1181bcd0d2572aee2c0947040e56bc1f9af634e3
Comments
> -----Original Message----- > From: Gdb-patches <gdb-patches- > bounces+mikhail.terekhov=dell.com@sourceware.org> On Behalf Of Simon > Marchi via Gdb-patches > Sent: Tuesday, October 3, 2023 10:04 PM > To: gdb-patches@sourceware.org > Cc: Simon Marchi <simon.marchi@polymtl.ca> > Subject: [PATCH 0/3] Add assertion when marking the remote async flag > > I had this idea while reviewing this patch [1]. When marking the remote > async flag, assert that the target is actually in async mode, instead of relying > on an assert that comes at a later time, in the wait method. After applying this series GDB fails in my setup in assert in mark_async_event_handler right after call to it from queued_stop_reply. See my comment to PATCH 3/3. > The first two patches are small preparatory refactorings, and the third one > adds the assertion. > > [1] https://urldefense.com/v3/__https://inbox.sourceware.org/gdb- > patches/3d728a6e-1cb0-49c2-a4c8- > 0a974be39fee@simark.ca/T/*ma1903117423ae09c3574fd45ade2dd4af528063 > 3__;Iw!!LpKI!kBSMETr5QzzmvTDT4A0kxAcpgnOpWd2ZyualTzxDwp42So5Om > byWvIb9bglZjsO4OCDKV_fIXMUj- > Yh5Q6PUPj26WV9J$ [inbox[.]sourceware[.]org] > > Simon Marchi (3): > gdb: make remote_state's async token private > gdb: add remote_state::{is_async_p,can_async_p} > gdb: add assertion when marking the remote async flag > > gdb/remote.c | 93 ++++++++++++++++++++++++++++++++++---------------- > -- > 1 file changed, 62 insertions(+), 31 deletions(-) > > > base-commit: 1181bcd0d2572aee2c0947040e56bc1f9af634e3 > -- > 2.42.0 Internal Use - Confidential