From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id OPU3HOTdq2T5mxwAWB0awg (envelope-from ) for ; Mon, 10 Jul 2023 06:31:00 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=MvAtX2w0; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 649571E0BD; Mon, 10 Jul 2023 06:31:00 -0400 (EDT) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 50AE01E00F for ; Mon, 10 Jul 2023 06:30:58 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 80CBC3857704 for ; Mon, 10 Jul 2023 10:30:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 80CBC3857704 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688985057; bh=uF6oLHvzak+iUZ3+RqbJL3a2rmtTGML5OxREmoEYWAc=; h=To:Subject:In-Reply-To:References:Date:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=MvAtX2w0Y+0IorsRwQASYIdeuK8L+qyNsVIUffzSM47tqWOCrHk8iGJsnhkAUIyAq 2rykFLXi5LX1E03gp3/U2c4d/FiniTekmZ95KdAaUL/nccEyDvWRgVMSb32YeSn/eq kR++irre71d5rF1gjrfgwCZ0CxigdqKT+MyJuOAg= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id DD2973858D32 for ; Mon, 10 Jul 2023 10:30:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DD2973858D32 Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-475-bCSXLuW7NcqF9-NMsrg9lQ-1; Mon, 10 Jul 2023 06:30:37 -0400 X-MC-Unique: bCSXLuW7NcqF9-NMsrg9lQ-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-315935c808bso609876f8f.1 for ; Mon, 10 Jul 2023 03:30:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688985036; x=1691577036; h=mime-version:message-id:date:references:in-reply-to:subject:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=uF6oLHvzak+iUZ3+RqbJL3a2rmtTGML5OxREmoEYWAc=; b=jByiLkidSn6b5euhB9oAQ99RR+9Wkbn7JJJuJ5Ir4GARwIwZKizVQP9aks1Yjg0StT 8V+q+jd6MCVo35Kk7W0kNHFcm5JSp5tWUc/9QpGhrw92ZcAlTvYAtZYzXW7TKo/9ZZ81 56OhXfTFLGTp6K1f7U4J7W0zFOgnTnfZCCMUHGIcEHaVg1XxW2puxe7+F6BJyIyueo8U 4BmhqT9wfUQs9LJhdk/F9dVjlT4NLJCLIQ6EDuYKXRoS2eGQil5qs8wVI7WMT3uQxTqn YHApZZvHwXiwZJS5MxFTMiQc14xM6cYrXc9CVXYMISPUMCHYSJaBRCUi7blOcFvdnfrF l3Uw== X-Gm-Message-State: ABy/qLYRtN5DUPDtrDZK+HQWnLNSaaM1ZTAl0v5txg9kJQAyJYpKEnFN UgLVi0zqjHBxZH2JY4bMMFsc3rZH040w9NmqgHRMZas9G+bKDZDS5u5cjryBuO0Euf1milQcafx tj/wvlXDvgc1h+rqjwM7dfdqn0JXssg== X-Received: by 2002:a5d:590f:0:b0:313:ed10:7f52 with SMTP id v15-20020a5d590f000000b00313ed107f52mr14685723wrd.18.1688985035896; Mon, 10 Jul 2023 03:30:35 -0700 (PDT) X-Google-Smtp-Source: APBJJlFHIU39ln5Y+FFskZQWgLHKo0M7D9cbA7PJHwR0kAjZL1wQK3MKfSsuF4oDDRleN2HBvRegcw== X-Received: by 2002:a5d:590f:0:b0:313:ed10:7f52 with SMTP id v15-20020a5d590f000000b00313ed107f52mr14685709wrd.18.1688985035621; Mon, 10 Jul 2023 03:30:35 -0700 (PDT) Received: from localhost (2.72.115.87.dyn.plus.net. [87.115.72.2]) by smtp.gmail.com with ESMTPSA id o2-20020a5d4742000000b0031434936f0dsm11309552wrs.68.2023.07.10.03.30.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Jul 2023 03:30:34 -0700 (PDT) To: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [PATCHv5 01/11] gdb: include breakpoint number in testing condition error message In-Reply-To: <35169d2a-bd73-d1cc-c0a8-3e8b85618292@palves.net> References: <24b51a1fbfc6f8b8cc52e3f90d4f36c1d44aaa6b.1678987897.git.aburgess@redhat.com> <3012ae0b-ac62-1b19-e56a-00129205393b@palves.net> <87sf9zk9rs.fsf@redhat.com> <35169d2a-bd73-d1cc-c0a8-3e8b85618292@palves.net> Date: Mon, 10 Jul 2023 11:30:33 +0100 Message-ID: <87h6qcjbxy.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE 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.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Andrew Burgess via Gdb-patches Reply-To: Andrew Burgess Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Pedro Alves writes: > On 2023-07-07 16:43, Andrew Burgess wrote: >> Pedro Alves writes: > >>> Reading this, I was thinking that we should print the breakpoint location number >>> as well. We do print it when presenting breakpoint stops nowadays, like: >>> >>> (top-gdb) b printf >>> Breakpoint 3 at 0xee680 (2 locations) >>> (top-gdb) r >>> ... >>> Breakpoint 3.1, ui_file::printf ... >>> ... >>> >>> Did you consider that and decided against? I didn't find any mention of it in previous >>> discussions. >> >> No, this was just an oversight, and would I think be a great >> improvement. >> >> The patch below implements this idea. Let me know what you think. > > Looks good, thanks! > > Approved-By: Pedro Alves Pushed. Thanks, Andrew