From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) by sourceware.org (Postfix) with ESMTPS id 93ABD3858D32 for ; Fri, 13 Jan 2023 12:59:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 93ABD3858D32 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f44.google.com with SMTP id r2so20993117wrv.7 for ; Fri, 13 Jan 2023 04:59:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=R+27uQrsr1VE9a4UvugQMrzbAQGkBWO6OLXnEysWnvk=; b=W4V8uYRMp9oPE7YNaLEJ8YXhcVL2HyNFRdsV89hNhh3AKmldnZ8LCDeyMqR82NEISg qUI50+N4BOto/kzsNMs2wTWRRjSSG8PDLONBen9WyFIXAhfD88luTuGThohmhmjK0EuW AJYfO75FV/vN043jbRD+FhujhefVEB9vbo9Z8a/tawFALsu0/mKFAR1sEpMxfRSBLxrS msjznOTY8UxoX8DOMpk1KjHwAcnRaXmoB5rgm8KppafVykW3atBKZ+iITw8Ph+LVGXRY nzh89URdvUq2wuOJRUCg4R3r2ZikGoZmUJIPhkdSyAr3DKnD69/S+ktANAiW8sjKSdd0 c/cw== X-Gm-Message-State: AFqh2kqDewG0iDQ+hFwRUqIldaC1jfjxuRVxSsmDiJBUSC0FFoz73ECR zGFfmRfAsOeFECfDQdQ5jn1BeCIxBySBbQ== X-Google-Smtp-Source: AMrXdXu236HfBB2bVQDltj6LRO6G1ZFpVDLFbUDd1YifZ0QCZqQKvH6RRkcTiB1ptn52VLgqwpuqgw== X-Received: by 2002:adf:9b96:0:b0:2bd:da88:f7a0 with SMTP id d22-20020adf9b96000000b002bdda88f7a0mr2959689wrc.32.1673614790363; Fri, 13 Jan 2023 04:59:50 -0800 (PST) Received: from ?IPv6:2001:8a0:f92b:9e00::1fe? ([2001:8a0:f92b:9e00::1fe]) by smtp.gmail.com with ESMTPSA id bo30-20020a056000069e00b0027a57c1a6fbsm19180318wrb.22.2023.01.13.04.59.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Jan 2023 04:59:50 -0800 (PST) Subject: Re: [PATCH 3/3] Let Python breakpoints be created silently To: Tom Tromey , gdb-patches@sourceware.org References: <20221208191804.3819129-1-tromey@adacore.com> <20221208191804.3819129-4-tromey@adacore.com> From: Pedro Alves Message-ID: Date: Fri, 13 Jan 2023 12:59:48 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <20221208191804.3819129-4-tromey@adacore.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,KAM_DMARC_STATUS,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP 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: On 2022-12-08 7:18 p.m., Tom Tromey via Gdb-patches wrote: > Currently, a breakpoint created from Python will always announce its > presence; and in some cases (for example a pending breakpoint), other > information will be printed as well. > > When scripting gdb, it's useful to be able to control the output in > cases like this. I debated whether to simply disable the output > entirely, but I thought perhaps some existing code acts as a simple > "break"-like command and wants the output. > > This patch adds a new "announce" flag to gdb.Breakpoint. Setting this > to False will cause gdb to be silent here. Wouldn't making the breakpoint "internal" work for the same effect?