From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound-ss-820.bluehost.com (outbound-ss-820.bluehost.com [69.89.24.241]) by sourceware.org (Postfix) with ESMTPS id 1F9B83858D38 for ; Sun, 23 Jul 2023 19:54:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1F9B83858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw13.mail.unifiedlayer.com (unknown [10.0.90.128]) by progateway2.mail.pro1.eigbox.com (Postfix) with ESMTP id 6A29510046B31 for ; Sun, 23 Jul 2023 19:54:14 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id Nf9iqBSr6sBigNf9iqWZzM; Sun, 23 Jul 2023 19:54:14 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=DqGTREz+ c=1 sm=1 tr=0 ts=64bd8566 a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=OWjo9vPv0XrRhIrVQ50Ab3nP57M=:19 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=ws7JD89P4LkA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=nZ4Od14MQ_KTodOuCVQA:9 a=zZCYzV9kfG8A:10:nop_mobile_phish_fin_urg DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=fPqJexKPVvDTPBu7/Y12HwIvpLsQS47hYny3Q3ciliY=; b=f192GHO4wnra902BY/u1DHfzUY w0C8QE86c+DESfG+Je7xY2eHLjxA1MLi082btGs1lODCa1YXFtXkuN39Oy16q+/3bJSwGFdMxe95W J6r42E8+Qot51w361vhr7NLx3; Received: from 75-166-135-140.hlrn.qwest.net ([75.166.135.140]:52172 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1qNf9i-000txr-0G; Sun, 23 Jul 2023 13:54:14 -0600 From: Tom Tromey To: Matheus Branco Borella via Gdb Cc: Matheus Branco Borella Subject: Re: Disabling warnings for certain operations References: X-Attribution: Tom Date: Sun, 23 Jul 2023 13:54:13 -0600 In-Reply-To: (Matheus Branco Borella via Gdb's message of "Wed, 19 Jul 2023 20:54:00 -0300") Message-ID: <87cz0i9zfe.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 75.166.135.140 X-Source-L: No X-Exim-ID: 1qNf9i-000txr-0G X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 75-166-135-140.hlrn.qwest.net (prentzel) [75.166.135.140]:52172 X-Source-Auth: tom+tromey.com X-Email-Count: 5 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3019.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,JMQ_SPF_NEUTRAL,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Matheus> As a workaround, I've hacked around GDB a bit, and added an option in Matheus> `target.c` (set through `set print-default-memory-search-warnings Matheus> off`) to suppress the warning message when `simple_search_memory` is Matheus> called from `default_search_memory`. Ideally, I'd like to submit some Matheus> form of achieving this as a patch, but the current solution feels Matheus> hacky and rough. TBH I'd expect reading inaccessible memory to throw a Python exception. Matheus> Is there a better way to do this? Or some way to query whether a range Matheus> can be read ahead of time so that calling `gdb.Inferior.search_memory` Matheus> may be skipped for those ranges, avoiding the path that would trigger Matheus> the warning altogether? I wonder if "info proc mappings" could be used somehow, or extended to provide some Python API. Anyway I think doing something here would be great -- the real question is just which approach is both useful and doable. Tom